[Bioc-devel] Package update failure because of version numbering

Martin Morgan mtmorg@n@bioc @ending from gm@il@com
Thu Sep 20 12:27:10 CEST 2018

On 09/18/2018 07:03 AM, Holger Schwender wrote:
> Dear all,
> I've tried to update devel version 1.51.2 of my Bioconductor package logicFS. Since this is a very major update (with several new features), I've found it a good idea to also show this with the version numbering and gave the new version the number 2.1.9 (.9 since we've updated the package step-by-step locally).
> When committing the changes to Bioconductor, I've however got an error from git push upstream master that this change in version numbering is not allowed/possible.
> Is it nethertheless somehow possible to increase the version number from 1.51 to 2.1? Or do I have to use 1.51.z? (More importantly, is it somehow possible that the next release version is 2.2.0 or 2.0.0?)

If the package has been publicly available outside Bioconductor at 
version 2.1.9 then I think you really want to always increment 'up', so 
something larger than that, such as 2.1.10. This will become 2.2.0 in 
the next release.

To get the 2.0.0 version, one would make the (allowed) change 1.99.0 and 
then increment z. This will be bumped to 2.0.0 at release. This would be 
appropriate only if version numbers less than 1.99.0 have been used already.

A good practice for local changes in this scenario might be to increment 
a final 'w' etc version before committing 1.51.3 to 

If you'd like to increment your Bioconductor package to 2.1.10, please 
let me know and I'll make the change; you can then pull the update to 
your local repository.


> Thanks a lot,
> Holger
> _______________________________________________
> Bioc-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel

More information about the Bioc-devel mailing list