If nobody objects I will send a official email to user@ and dev@ to declare all of the release lines prior to 4.14.x as EOL: - no more releases - no more security fixes - no more patches committed to those branches
I don't think we need a VOTE for this given this discussion. I will also update the website. This will happen early next week Best regards Enrico Il giorno ven 30 set 2022 alle ore 19:57 Andrey Yegorov <andrey.yego...@datastax.com> ha scritto: > > I agree. > > Upgrades from 4.11+ up to 4.14 are straightforward (e.g. DataStax's fork of > Pulsar 2.7 uses BK 4.14). > BK 4.15 has breaking API changes so we'll need to keep 4.14 alive for a > while. > > On Mon, Sep 26, 2022 at 11:43 PM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > Hello, > > I propose to declare end-of-life on all the release lines prior to 4.14. > > > > We wanted to follow a time-based release plan, but actually we are not > > following it. > > > > This is the doc on our website > > https://bookkeeper.apache.org/community/releases > > > > If nobody objects, I will start a separate thread with a VOTE for this > > resolution. > > > > End-of-life generally means "no more releases" so: > > - no more bug fixes > > - no more security fixes > > - no patches accepted to be cherry-picked to those branches > > > > Please chime in with your thoughts > > > > Enrico > > > > > -- > Andrey Yegorov
