A reasonable strategy is to create a branch ('master' for submission) that
contains just the package source; use another branch for additional
functionality.
After submission, your package is cloned to the git.bioconductor.org repository
and you could maintain it from an arbitrary branch in you
If you're asking because you're thinking about package development, then this
would be the right place ;) there are answers on the support site, though...
Martin
On 8/31/20, 11:37 AM, "Bioc-devel on behalf of Augustin Luna"
wrote:
Is the ExpressionSet class deprecated? If it is, what are
Is the ExpressionSet class deprecated? If it is, what are the
ramifications of this?
* Are new packages barred from using ExpressionSet?
* Will existing packages that use ExpressionSet be forced to move to
SummarizedExperiment? If so, when?
* Often deprecation means the removal of support. If Expr
Hi to all,
My team is just about to submit a new package to Bioconductor and we have
a question about the files included in the github repository: According to
Bioconductor Guidelines for package submission, the repo should not contain
unnecessary files other than the required for package installa
Hi,
My name is Stephan Fischer, I'm a postdoc at CSHL with Dr Jesse Gillis
and I'm currently maintaining the internal version of the MetaNeighbor
package. The Bioconductor version of the package was previously
maintained by Manthan Shah, who left the lab about a year ago. I would
like to take
