On Tue, Jun 20, 2023 at 1:34 AM Henrik Bengtsson
wrote:
> On Mon, Jun 19, 2023 at 5:46 PM Vincent Carey
> wrote:
> >
> > Hi Adam, thanks for your note.
> >
> > Changes to release branch sources must be limited to bug fixes or doc
> > improvement. Any new features
> > must be introduced only in
On Mon, Jun 19, 2023 at 5:46 PM Vincent Carey
wrote:
>
> Hi Adam, thanks for your note.
>
> Changes to release branch sources must be limited to bug fixes or doc
> improvement. Any new features
> must be introduced only in the devel branch.
I know about this, but I wanted to find what the
I'd also add, that I've had a version of a package that specifically
implemented things just for a manuscript, because they were kind of hackish
implementations to prove that it was possible. I made that available in a
specific branch of the package code on GitHub, and an archived version on
... And as a reviewer I'd never have an issue if a paper describes
something and mentions in which Version (x.y.z) it is released,
regardless in what BioC release/devel that is.
Yours,
Steffen
On Mon, 2023-06-19 at 11:46 -0400, Vincent Carey wrote:
> Hi Adam, thanks for your note.
>
> Changes
Hi Adam, thanks for your note.
Changes to release branch sources must be limited to bug fixes or doc
improvement. Any new features
must be introduced only in the devel branch. Any features to be removed
must be indicated as
deprecated for one release and then labeled as defunct. See
Hi all,
I wonder if there is any room for deploying a modification to a released
library(retrofit, 3.17), which was released last month.
We are in a progress of a paper review, so the release schedule (twice each
year) does not perfectly fit our need.
Or do you think we should have used