[Bioc-devel] Managing Multiple GitHub Branches the Bioconductor Way
Lor|@Shepherd @end|ng |rom Ro@we||P@rk@org
Wed Apr 24 13:04:26 CEST 2019
#17 of the FAQ http://bioconductor.org/developers/how-to/git/faq/
You personally can create as many branches as you like for your own use.
We recommend the following and these are the upstream branches to link to:
Bioconductors stable release version should be on a branch RELEASE_3_9 (create a new one when the next release comes out, i.e RELEAES_3_10)
Biconductors development branch should be on the master branch
Each branch RELEASE_X_Y would support the previous stable versions of the package.
BiocManager will access the version the package was released under and greater. Users of previous versions of R (if you support that) would have to install your github repository which can be done through the install function. ie. install("githubAccount/packagename").
Bioconductor Core Team
Roswell Park Cancer Institute
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
From: Bioc-devel <bioc-devel-bounces using r-project.org> on behalf of Federico, Anthony, Nicholas <anfed using bu.edu>
Sent: Tuesday, April 23, 2019 9:06:03 PM
To: bioc-devel using r-project.org
Subject: [Bioc-devel] Managing Multiple GitHub Branches the Bioconductor Way
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?
Bioc-devel using r-project.org mailing list
This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.
[[alternative HTML version deleted]]
More information about the Bioc-devel