Message-ID: <CAMFmJs=VOPy00HJ23AwjUv1b_fodG9tce_G_LM7yCh+ess4tzA@mail.gmail.com>
Date: 2018-04-03T15:56:01Z
From: Gabriel Becker
Subject: [Bioc-devel] Missed deadline
In-Reply-To: <CAOUXvx7AuofuC_bb7cTBuo0XgbjK71Ldm=9eYti0QzPA9AqrHA@mail.gmail.com>
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, Levi Waldron <lwaldron.research at gmail.com>
wrote:
> On Tue, Apr 3, 2018 at 5:32 AM, Kenneth Condon <roonysgalbi at gmail.com>
> 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 sure if development is far enough
> > along, although I suspect it might be.
> >
>
> IMHO, when you're not sure a package is mature enough, and especially for a
> first package, it's actually better to miss the release deadline and allow
> bioc-devel users test your package for 6 months before entering the release
> cycle. Making significant bug fixes and other changes becomes more
> complicated and more of a pain for you and your users once you are in the
> release...
>
> [[alternative HTML version deleted]]
>
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>
>
--
Gabriel Becker, Ph.D
Scientist
Bioinformatics and Computational Biology
Genentech Research
[[alternative HTML version deleted]]