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
On Fri, Feb 23, 2018 at 8:24 PM, Nicolas Descostes <
> 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.
> [[alternative HTML version deleted]]
> Biocemail@example.com mailing list
Department of Bioinformatics - BiGCaT
Maastricht University (http://www.bigcat.unimaas.nl/)
ORCID: 0000-0001-7542-0286 <http://orcid.org/0000-0001-7542-0286>
[[alternative HTML version deleted]]
Biocfirstname.lastname@example.org mailing list