[Bioc-devel] Question about inclusion in upcoming bioconductor

Hervé Pagès hpages at fredhutch.org
Fri Sep 22 23:35:58 CEST 2017

Hi Jason,

Note that https://bioconductor.org/developers/how-to/git/ has a
collection of documents that cover all the aspects of maintaining
a Bioconductor package via git/GitHub.

In particular see "New package workflow" for what to do after package
acceptance and "Push to GitHub and Bioconductor repositories" for
everyday development of your package.

I hope you'll find these documents as helpful as I do.


On 09/17/2017 11:15 AM, Shepherd, Lori wrote:
>    1.  Yes. If you package was accepted and is on git at git.bioconductor.org then it is set to be included in the next release version of Bioconductor. You do not need to do anything; the Bioconductor team will handle making appropriate branches to the repository.
>    2.   You can add changes to Bioconductor devel at any time. The master branch of the repository is the devel branch of Bioconductor.  If you push changes to the master branch of your package on git at git.bioconductor.org (with appropriate version bump)  it will be reflected in the next Bioconducotor devel build report.
> Cheers,
> Lori Shepherd
> Bioconductor Core Team
> Roswell Park Cancer Institute
> Department of Biostatistics & Bioinformatics
> Elm & Carlton Streets
> Buffalo, New York 14263
> ________________________________
> From: Bioc-devel <bioc-devel-bounces at r-project.org> on behalf of Weirather, Jason L. <JasonL_Weirather at DFCI.HARVARD.EDU>
> Sent: Friday, September 15, 2017 10:45:18 AM
> To: bioc-devel at r-project.org
> Subject: [Bioc-devel] Question about inclusion in upcoming bioconductor
> Dear Bioconductor Team,
> I had a couple of quick questions
> 1) Is our package set to go into the next Bioconductor if it�s made it through the submission process and we have access to the Bioconductor git repository? Is the master branch for that properly staged for the upcoming release, or do we need to do anything else like make some release branch or tick version or anything like that?
> 2) If I want some newer changes to go into Bioconductor devel, do I just make a devel branch on the git repository?
> For context, I have recently helped Dr. Dan Gusenleitner with submission of the �IrisSpatialFeatures� package.  Now the package has made it through the pipeline to be accepted, and I have access to the bioconductor git repository for our package.
> We are excited it for it to make it out into the wider community and just wanted to make sure we have is staged properly.
> Thank you for your advice,
> Jason
> The information in this e-mail is intended only for the ...{{dropped:28}}
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://urldefense.proofpoint.com/v2/url?u=https-3A__stat.ethz.ch_mailman_listinfo_bioc-2Ddevel&d=DwICAg&c=eRAMFD45gAfqt84VtBcfhQ&r=BK7q3XeAvimeWdGbWY_wJYbW0WYiZvSXAJJKaaPhzWA&m=nFb1r1fuYCP2GwrmK1xrKpRlaE2bjS3E__V987nmKwY&s=tCjzgXgKTGsswh3CuOknOsv1UGvFJFrTqrmpot-AHPk&e=

Hervé Pagès

Program in Computational Biology
Division of Public Health Sciences
Fred Hutchinson Cancer Research Center
1100 Fairview Ave. N, M1-B514
P.O. Box 19024
Seattle, WA 98109-1024

E-mail: hpages at fredhutch.org
Phone:  (206) 667-5791
Fax:    (206) 667-1319

More information about the Bioc-devel mailing list