[Bioc-devel] Few questions of maintaining a new bioconductor package

Nitesh Turaga ntur@g@@b|oc @end|ng |rom gm@||@com
Fri Sep 18 16:25:10 CEST 2020


You will not have to do anything once your package is accepted.  http://bioconductor.org/developers/package-submission/ <http://bioconductor.org/developers/package-submission/> . Almost all your queries are answered in this help page.

1. To trigger a new build, include a version bump in your commit, e.g., from Version: 0.99.0 to Version: 0.99.1. Pre-release versions utilize the 0.99.z format. When accepted and released, your package’s version number will be automatically incremented to 1.0.0.

2. You have to wait for the nightly build. The faster way is your check your package locally with R CMD build and R CMD check. 

3. You will have to activate your BiocCredentials account, if you are a first time contributor. 



> On Sep 18, 2020, at 5:01 AM, Krutik Patel (PGR) <K.Patel5 using newcastle.ac.uk> wrote:
> Dear Bioconductor team,
> I've recently had my package, TimiRGeN, accepted into bioconductor and have a few questions on the maintenance side of things.
> 1) I am ready to push a newer version of the package. Will I have to set the version to 1.0.0 now? Currently it is version 0.99.4158.
> 2) Once pushed, how can I check if the build has been successful? Will I have to wait and see if it has passed the nightly builds on build/checkResults? Or is there a faster method.
> 3) I would like to set up a new SSH key and use this to maintain my package. To do this I will need to activate my account on Bioconductor Git Credentials, but I do not remember setting up a password for this.
> Any help in these matters would be great.
> Best,
> Krutik
> 	[[alternative HTML version deleted]]
> _______________________________________________
> Bioc-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel

	[[alternative HTML version deleted]]

More information about the Bioc-devel mailing list