[Bioc-devel] Urgent minor deployment of a release?

Vincent Carey @tvjc @end|ng |rom ch@nn|ng@h@rv@rd@edu
Tue Jun 20 13:17:51 CEST 2023


On Tue, Jun 20, 2023 at 1:34 AM Henrik Bengtsson <henrik.bengtsson using gmail.com>
wrote:

> On Mon, Jun 19, 2023 at 5:46 PM Vincent Carey
> <stvjc using channing.harvard.edu> 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 document exactly says
> about this. I'm sure it's documented somewhere, but I just spend 10-15
>

I agree with your conclusion here.  I don't think this is documented in the
contributions.bioconductor.org.  I am sorry about the 15 minutes, I should
have commented when I responded that we need to improve the doc
on this.


> min on the website trying, but I couldn't find it.  What I was looking
> specifically for was "new features".  For instance, would one be
> allowed to introduce a 100% backward compatible new features to the
> Bioc release branch? For instance, assume you currently have
>
> h <- function(x, ...) {
>   sum(x)
> }
>
> in the release branch, would it be okay to add:
>
> h <- function(x, na.rm = FALSE, ...) {
>   sum(x, na.rm = na.rm)
> }
>
> ?  This is how base-R itself does it in their patch releases, e.g. R
> 4.3.0 -> R 4.3.1.
>

The intent is that the APIs for packages in the release branch be "stable".
Let's discuss how to formalize and document this intent.


>
> /Henrik
>
> > Any features to be removed
> > must be indicated as
> > deprecated for one release and then labeled as defunct.  See
> >
> > http://contributions.bioconductor.org/deprecation.html
> >
> > for guidan
> > Changes to release branch sources must be limited to bug fixes or doc
> > improvement.
> > ce on feature removal.
> >
> >
> > On Mon, Jun 19, 2023 at 10:11 AM Park, Adam Keebum <sein.park using psu.edu>
> > wrote:
> >
> > > 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 "devel" for such purposes?
> > >
> > > Sincerely,
> > > Adam.
> > >
> > >         [[alternative HTML version deleted]]
> > >
> > > _______________________________________________
> > > Bioc-devel using r-project.org mailing list
> > > https://stat.ethz.ch/mailman/listinfo/bioc-devel
> > >
> >
> > --
> > The information in this e-mail is intended only for the ...{{dropped:18}}
> >
> > _______________________________________________
> > Bioc-devel using r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/bioc-devel
>

-- 
The information in this e-mail is intended only for the ...{{dropped:18}}



More information about the Bioc-devel mailing list