[Bioc-devel] Best practices for joint release/update of BioC packages

Russell Bainer ru@@@b@|ner @end|ng |rom gm@||@com
Wed Aug 25 01:07:29 CEST 2021

Hello All,

I am planning a major update to my BioC package in the next release (
and some of the new functionality depends on another package that is being
submitted for acceptance by a collaborator.

All of the code in my package passes R/BioC check using the package in my
collaborator's github repo, but as his code has not yet been incorporated
into BioC my current build is failing.

What is the recommended way to deal with a situation like this? Obviously I
want to avoid deprecation of my own package, and obviously I could just
hide all of the parts of the update that depend on external code. But I
also think that my collaborator's work adds significantly to the utility of
my package, and I want to ensure that their contributions are properly
highlighted/celebrated in my 2.0 release.

Thanks in advance for the input.


	[[alternative HTML version deleted]]

More information about the Bioc-devel mailing list