Core packages go through the same review process as community contributed
packages, although many of the core packages pre-date the current github review
process.
Github seems to have been introduced in 2016. Before that we used the roundup
issue tracker system where packages were uploaded and reviewed by core team
members. I *think* the review process was public, but it would have been much
less visible than the current system.
I don't remember when the issue tracker was introduced, or how things were done
before that.
I think the single package builder (automatic check of submitted packages) was
introduced during this phase, maybe in the 2012 time frame.
Martin
On 6/9/19, 8:32 AM, "Bioc-devel on behalf of Lluís Revilla"
<bioc-devel-boun...@r-project.org on behalf of lluis.revi...@gmail.com> wrote:
Hi,
Recently I was looking how package reviews are done. Specifically those
packages from developers on the Bioconductor team, or listing the
Bioconductor Package Maintainer as the maintainer.
Some of those packages become the backbone of other packages and perhaps
there are some experiences on the reviewing the 50 packages that
Bioconductor is currently maintaining. However, I couldn't find if there
are under the same review process than other packages? Or are there any
other expectations on the review of those packages?
Sorry if this has been described before, I couldn't come up with a good
search term, and didn't find anything on the Package Submission website.
And as a fairly new contributor I don't know how package reviews were done
before github.
Many thanks,
Lluís
[[alternative HTML version deleted]]
_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
