I am guilty of doing this today, but I have (I think) a good reason.
I'm making a bunch of changes that are all related to each other, but
are being implemented and tested in stages. I'd like to use svn to
commit when I've made a set of changes that works, so I can roll back if
I break something in the next step, but I'd like the users to see them
all at once as a single version update. Perhaps others are doing
something similar?
Stephanie
On 9/4/14, 12:04 PM, Dan Tenenbaum wrote:
Hello,
Looking through our svn logs, I see that there are many commits that are not
accompanied by version bumps.
All svn commits (or, if you are using the git-svn bridge, every group of commits included
in a push) should include a version bump (that is, incrementing the "z" segment
of the x.y.z version number). This practice is documented at
http://www.bioconductor.org/developers/how-to/version-numbering/ .
Failure to bump the version has two consequences:
1) Your changes will not propagate to our package repository or web site, so
users installing your package via biocLite() will not receive the latest
changes unless you bump the version.
2) Users *can* always get the current files of your package using Subversion,
but if you've made changes without bumping the version number, it can be
difficult to troubleshoot problems. If two people are looking at what appears
to be the same version of a package, but it's behaving differently, it can be
really frustrating to realize that the packages actually differ (but not by
version number).
So if you're not already, please get in the habit of bumping the version number
with each set of changes you commit.
Let us know on bioc-devel if you have any questions about this.
Thanks,
Dan
_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
