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 th
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
wrote:
> Hello,
> I propose to declare end-of-life on al
I Agree.
> I propose to declare end-of-life on all the release lines prior to 4.14.
I think we should have a clear end-of-life policy for BookKeeper.
> For me having two release lines is acceptable.
We'd better not define the end-of-life policy based on the release lines number.
Thanks,
Hang
Agree.
>In my opinion we should formalize this process in order to have a clear
vision when 4.16.0 will be out.
This will also help users to understand the entire lifecycle of the
project.
For me having two release lines is acceptable.
I think that depends on how long we will stay on a major vers
Makes sense to me. Is the upgrade path straightforward? For example,
Apache Pulsar 2.7.5 currently uses release line 4.12, so it would need
to be upgraded to at least 4.14 if we wanted to stay on a supported
version.
Thanks,
Michael
On Tue, Sep 27, 2022 at 3:08 AM steven lu wrote:
>
> +1 I agre
+1 I agree.
Nicolò Boschi 于2022年9月27日周二 16:00写道：
> I agree. And it actually reflects what we're doing in the community (only
> cherry-pick to branches 4.14 and 4.15).
>
> In my opinion we should formalize this process in order to have a clear
> vision when 4.16.0 will be out.
> This will also he
I agree. And it actually reflects what we're doing in the community (only
cherry-pick to branches 4.14 and 4.15).
In my opinion we should formalize this process in order to have a clear
vision when 4.16.0 will be out.
This will also help users to understand the entire lifecycle of the
project.
Fo
