Hi Nicolas, after doing a bit of work on the BridgeDbR package this weekend, I was wondering exactly the same thing. I prefer small patches, so that I can easily link the change with the commit message and have related changes together (and fairly, it allows me to see when I actually work on what (#academicTimeReporting)... But previously I learned that when you push something to the repository, you should bump the question, so currently I do this for every change I made, leaving a ridiculous number of minor release and really short NEWS entries...
Working in a branch and when only bumping the version number just before the merge into master makes a lot of sense to me. Can some senior developer and/or gatekeeper confirm that that is acceptable commit practice? Egon On Fri, Feb 23, 2018 at 8:24 PM, Nicolas Descostes < nicolas.descos...@gmail.com> wrote: > Dear Bioconductor community, > > When developing further a package, is the best practice to create a branch > and bump the version when a full new feature is merged or to stay on the > master without bumping when committing temporarily? More generally, When do > you usually bump a version? > > Thank you. > > Nicolas > > [[alternative HTML version deleted]] > > _______________________________________________ > Bioc-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/bioc-devel > -- E.L. Willighagen Department of Bioinformatics - BiGCaT Maastricht University (http://www.bigcat.unimaas.nl/) Homepage: http://egonw.github.com/ LinkedIn: http://se.linkedin.com/in/egonw Blog: http://chem-bla-ics.blogspot.com/ PubList: https://www.zotero.org/egonw ORCID: 0000-0001-7542-0286 <http://orcid.org/0000-0001-7542-0286> ImpactStory: https://impactstory.org/u/egonwillighagen [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
