Kenneth,
I agree with Kasper. I generally like the approach of getting the software
out there sooner rather than later. Especially if the paper you are talking
about is a method paper about the software algorithm, rather than a result
paper. In that case, getting it into a public, DOI'ed
This is a subjective question. As a paper reviewer I like to see the
package accepted. That increases trust. As a package reviewer I like some
idea of what the package actually does, so a statement like "we implement X
which is described in (XX, in preparation), is also irritating.
Unless you're
Hi Gabe & Levi,
Here is my current plan:
1 - complete the requirements checklist (
http://www.bioconductor.org/developers/package-submission/)
2 - get feedback the in-house NGS team, and then from the rest of in-house
bioinformatics (others who use R more may spot some issues)
3 - set up pull
ONE more note that Gabe reminded me of! As soon as your package is accepted
into bioc-devel, it will be accessible via
https://bioconductor.org/packages/mypackage/. Once it enters the release
branch, that URL will instead point to the release page.
On Tue, Apr 3, 2018 at 11:56 AM, Gabe Becker
Indeed, and to be a bit more explicit about Levi's point, you *can* publish
your package to bioconductor any time after the deadline, it will simply go
to the development repo for ~6 months, which, as he points out, may not be
a bad thing if it's not ready yet.
On Tue, Apr 3, 2018 at 8:06 AM,
On Tue, Apr 3, 2018 at 5:32 AM, Kenneth Condon
wrote:
> Have I missed the deadline for the latest release? I have created a
> package, that runs great but there are a number of errors still from R CMD
> check that I am sorting out.
>
> This is my first R package so I'm not
The deadline to submit new packages for this release was yesterday. You could
still submit the package for review but there is no guarantee it will make it
through the review process in time to be included as reviewers will focus on
packages that made the deadline. The last day for the newly