Hi Alan,
What you have written below looks correct to me. A simpler way to remember this is how the versioning works - (X.Y.Z) or (major.minor.patch). You only every update the “patch” or the “Z” number in the versioning system. Best, Nitesh Nitesh Turaga Scientist II, Department of Data Science, Bioconductor Core Team Member Dana Farber Cancer Institute > On Jun 16, 2021, at 1:33 PM, Murphy, Alan E <a.mur...@imperial.ac.uk> wrote: > > Hi, > > I have a package EWCE(https://github.com/NathanSkene/EWCE) that was newly > published in Bioconductor in version 3.13. The release package version number > is 1.0.0. > > However, I have identified a bug in the package and need to push the fix to > the current release version and the devel version. This is my first time > doing this so I want to make sure I understand how to do it correctly. I have > read the information > here(http://bioconductor.org/developers/how-to/git/bug-fix-in-release-and-devel/) > about bug fixes and > here(http://bioconductor.org/developers/how-to/version-numbering/) regarding > version numbering. Based on these, I do have a specific question. My current > master branch is at version 1.1.0 for the devel branch while the release_3_13 > branch is version 1.0.0. Should I checkout out either branch separately, make > the fix and bump the versions (1.0.1 for release branch and 1.1.1 for the > master branch) and then push both upstream separately (git push upstream > <RELEASE_X_Y>/master) and afterwards push each to the repo (git push origin > <RELEASE_X_Y>/master)? > > Thanks, > Alan. > > > Alan Murphy > Bioinformatician > Neurogenomics lab > UK Dementia Research Institute > Imperial College London > > [[alternative HTML version deleted]] > > _______________________________________________ > 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
