[Bioc-devel] Bioconductor 3.1 release schedule now available

----- Original Message -----

From: "Kasper Daniel Hansen" <kasperdanielhansen at gmail.com>
To: "Tiphaine Martin" <tiphaine.martin at kcl.ac.uk>
Cc: "Dan Tenenbaum" <dtenenba at fredhutch.org>, "bioc-devel"
<bioc-devel at r-project.org>
Sent: Monday, March 16, 2015 6:43:40 PM
Subject: Re: [Bioc-devel] Bioconductor 3.1 release schedule now
available


If your package passes build and check without warnings it happens
automatically, including the version bump.

Yes, the only time you need to let us know is if you DO NOT want your
package in the release.

If this is the first release of your package, it should have a
version number of 0.99.Z (which seems to be the case). This is
checked / fixed when your package gets accepted.

Actually it's done during the release process. So your package will
remain at 0.99.z until the release but then in the new release branch it
will be 1.0.0 and in the new devel (trunk) it will be 1.1.0. See
http://bioconductor.org/developers/how-to/version-numbering/

Dan

Best,
Kasper


On Mon, Mar 16, 2015 at 9:29 PM, Martin, Tiphaine <
tiphaine.martin at kcl.ac.uk > wrote:


Dear Dan,

I have 2 naive questions.
I would like to know whether we (developers of a R package currently
only in the development version of Bioconductor) need to say that we
would like to have our packages accessible in the next version of
Bioconductor or it is automatic for any packages passing R CMD build
and check without warning.
If I have my new package that is going in the next release, should I
need to upgrade the version of my package ( from 0.99.Z to 1.0.0 )
and push it in svn or is it also done automatically ?

Regards,

Tiphaine