+1 for retiring the 3.6 release line after 3.6.4.

Máté, thank you for helping with the release!

Chris Nauroth


On Sat, Dec 3, 2022 at 10:21 AM Enrico Olivelli <eolive...@gmail.com> wrote:

> Mate,
>
> Il Sab 3 Dic 2022, 16:53 Szalay-Bekő Máté <szalay.beko.m...@gmail.com> ha
> scritto:
>
> > Hello!
> >
> > I think I can spare the time for starting the release process sometime in
> > the second part of next week.
> >
>
> Thanks! I will test it and VOTE
>
>
>
> > I see the last 3.6 release happened on 13 April, 2021 - pretty long ago.
> > There are plenty of tickets to ship, including the log4j -> reload4j
> > migration: https://issues.apache.org/jira/browse/ZOOKEEPER-4455
>
>
>
> This is very important
>
> >
> >
> > All tickets with fixVersion=3.6.4:
> >
> >
> https://issues.apache.org/jira/browse/ZOOKEEPER-4602?jql=project%20%3D%20ZOOKEEPER%20AND%20fixVersion%20%3D%203.6.4%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> >
> > Reading our official release strategy (
> > https://zookeeper.apache.org/releases.html), I am not exactly sure if /
> > when we should move branch 3.6 to EoL. Maybe after 3.6.4?
> >
> > What do you think?
> >
>
>
> I agree.
> The migration from 3.6.x to 3.8.x is pretty straightforward and anybody who
> is on 3.6 should be able to move to 3.8 pretty easily.
>
> There is no big reason to maintain the 3.6 branch
>
> Thanks for bringing up this discussion
>
> Enrico
>
>
> > Máté
> >
> >
> > On Thu, Dec 1, 2022 at 3:31 PM Enrico Olivelli <eolive...@gmail.com>
> > wrote:
> >
> > > Mark
> > >
> > > Il giorno sab 26 nov 2022 alle ore 17:57 Mark Sangster
> > > <markgsangs...@googlemail.com.invalid> ha scritto:
> > > >
> > > > Hi,
> > > >
> > > > Is there a planned release date for 3.6.4?
> > >
> > > Currently there is no plan.
> > > but if there is someone who needs it I believe that we can bootstrap
> > > the process.
> > >
> > > It is only a matter of finding a volunteer to cut the release.
> > >
> > > Anyone is willing to help here ?
> > >
> > > Enrico
> > >
> > > >
> > > > Mark
> > >
> >
>

Reply via email to