[Bioc-devel] New package version and BiocCheck

[Dan Tenenbaum]

Forgot to CC bioc-devel.

> > Hi Dan,
> > 
> > ----- Original Message -----
> > > From: "Dan Gatti" <Dan.Gatti at jax.org>
> > > To: bioc-devel at r-project.org
> > > Sent: Friday, April 18, 2014 9:32:12 AM
> > > Subject: [Bioc-devel] New package version and BiocCheck
> > > 
> > > I'm trying to submit a new package. I have set the version number
> > > to
> > > 0.99.0 as indicated at
> > > http://www.bioconductor.org/developers/package-submission/ .
> > > However, I get a warning from BiocCheck that says:
> > > 
> > > 
> > > * Checking new package version number...
> > >         * RECOMMENDED: y of x.y.z version should be even in
> > >         release
> > > 
> > > I tried changing the version to 0.98.0 and it told me that new
> > > packages must have a version of 0.99.0.  I see that the end of
> > > the
> > > warning says "in release", but I'm don't see a way to change the
> > > package status to development on the Issue tracking website.
> > > 
> > > I'm using the BiocCheck (v 1.1.1) that is currently on the
> > > submission
> > > site.  Can someone point me toward a solution?
> > > 
> > 
> > Ignore it for now.
> > 
> > The builder tied into the tracker probably needs to move to
> > machines
> > that are running the devel version of Bioconductor, but I don't
> > think this is going to happen right away.
> > 
> > I'll also try and come up with a better way to handle this
> > situation
> > so the messages about version number are less confusing.
> > 
> > Thanks,
> > Dan
> > 
> > 
> > OK, thanks.  This is my first Bioconductor submission, so I'm not
> > clear exactly how this works.  I have a data package that needs to
> > be in before the software package can build.  Should I wait for the
> > data package to be accepted and then try to build the software
> > package on the tracker?
> > 
> 
> The data package builds but it looks like there are some issues with
> the software package.
> 
> I'll volunteer to review this package and we can continue this
> conversation in the issue tracker.
> 
> Thanks,
> Dan
> 
>