Hi Michael, The Pulsar release policy [0] defines the Pulsar 2.10 release line, which has now been EOL. In fact, we still cherry-pick the commit to the branch-2.10 from the master, see [1].
I think the Pulsar 2.10 has been stable in the past few years, and can be run by using the JDK 8(Recommended version is JDK 11). The Pulsar 3.x requires the JDK 17. For enterprises to migrate JDK and Pulsar, they need to bear a significant cost. If we consider releasing the 2.10.6, I am willing to bump the Pulsar 2.10.6. [0] https://pulsar.apache.org/contribute/release-policy/#supported-versions [1] https://github.com/apache/pulsar/commits/branch-2.10/ Thanks, Zixuan Michael Marshall <mmarsh...@apache.org> 于2023年12月19日周二 14:26写道： > Hi Pulsar Community, > > Do we consider the 2.10 release line EOL? If not, is there a committer > that would like to volunteer to release 2.10.6? > > We briefly discussed keeping 2.10 alive in June [0], and that was > followed by a 2.10.5 release in July. Given that we already have 2.11, > 3.0, 3.1, and now a discussion on 3.2, it seems unsustainable to keep > 2.10 going much longer. > > Thanks, > Michael > > [0] https://lists.apache.org/thread/w4jzk27qhtosgsz7l9bmhf1t7o9mxjhp >
