In addition, next week is the Chinese New Year [1] in China and there is a long holiday (a week) for Chinese developers. I hope we can delay this release for a while.
[1] https://en.wikipedia.org/wiki/Chinese_New_Year Thanks, Yunze On Fri, Jan 20, 2023 at 10:23 AM Yunze Xu <y...@streamnative.io> wrote: > > I would like to include PIP-224 (even and PIP-229) in the next major > releases. These two PIPs have some impacts on the API and could bring > many benefits to ecosystem developers. But unfortunately the first PR > of PIP-224 [1] is still not reviewed by anyone. The code has already > been added locally and only requires some rebase to resolve conflicts. > > [1] https://github.com/apache/pulsar/pull/19158 > > Thanks, > Yunze > > On Fri, Jan 20, 2023 at 7:46 AM <mattisonc...@gmail.com> wrote: > > > > Isn't the next version LTS 3.0? > > > > Best > > Mattison > > On Jan 20, 2023, 07:11 +0800, Christophe Bornet <bornet.ch...@gmail.com>, > > wrote: > > > Hi Pulsar community, > > > > > > It's great that we released Pulsar 2.11. It has taken quite some time to > > > stabilize the release branch and now we have more than 5 months of awesome > > > features and commits on the master branch that would benefit a lot to our > > > users. That's why I'd like to propose to start a code freeze for the > > > release of Pulsar 2.12 with a target release date by mid/end-february. > > > Hopefully this release will be easier to stabilize but we don't know for > > > sure, so better to start the release activities asap. > > > We also need a release manager. Nicolo proposed himself last time but had > > > to hand over because of his holiday schedule. So Nicolo, maybe you'd like > > > to propose yourself again for this one ? Otherwise I'm happy to volunteer. > > > > > > Let me know what you think. > > > > > > Cheers > > > > > > Christophe
