[Bioc-devel] Managing Multiple GitHub Branches the Bioconductor Way
Federico, Anthony, Nicholas
@n|ed @end|ng |rom bu@edu
Wed Apr 24 03:06:03 CEST 2019
I have a basic question about structuring a GitHub repository for an accepted Bioconductor package that frequently adds new features. There would be three copies of the package.
1. Stable release currently on Bioconductor (Current version of R)
2. Developers branch for Bioconductor Devel (Next release of R)
3. A copy of the dev branch that supports prior versions of R
What would be the Bioconductor best practice for naming these three branches? Also does Bioconductor have a mechanism for allowing packages for previous versions of R to be installable through BiocManager?
More information about the Bioc-devel