I removed the "release/2.9.6" label from 50 PRs:
https://github.com/apache/pulsar/pull/20533
https://github.com/apache/pulsar/pull/20513
https://github.com/apache/pulsar/pull/20482
https://github.com/apache/pulsar/pull/20416
https://github.com/apache/pulsar/pull/20363
https://github.com/apache/pul
In light of this thread, I think we have a (lazy) consensus that 2.8
and 2.9 are EOL and we will continue to maintain 2.10.
Would someone be able to update the website to say that 2.10 is not EOL?
I will update the GitHub labels to indicate the 2.9 label should no
longer be used.
Thanks,
Michael
> This is the latest release that runs on JDK11
This point makes sense to me. Actually I think it's the latest release
that runs on JDK 8 though the recommended JDK for 2.10 is 11. The only
question from me is when should 2.10 be EOL?
Thanks,
Yunze
On Fri, Jun 9, 2023 at 3:15 PM Enrico Olivelli
Micheal,
Il giorno ven 9 giu 2023 alle ore 07:54 Michael Marshall
ha scritto:
>
> Hi Pulsar Community,
>
> I recently noticed this page on our website:
> https://pulsar.apache.org/contribute/release-policy/#supported-versions
>
> It shows that only 2.11 and 3.0 are active and security support.
>
Hi Pulsar Community,
I recently noticed this page on our website:
https://pulsar.apache.org/contribute/release-policy/#supported-versions
It shows that only 2.11 and 3.0 are active and security support.
I am guessing the timelines were taken from a strict reading of PIP
47. However, we haven't h
