On Thu, Jan 19, 2023 at 3:11 PM Christophe Bornet <bornet.ch...@gmail.com> wrote: > 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.
2.11 has just been released and the release cycle is set to 3 months. It's not a good idea to call for code freezes without appropriate warning, and code freezes don't make sense in general: the "master" branch must always be open for business. There was already a proposal to codify a formal release plan with prescribed timings for release RCs and stabilization. (https://github.com/apache/pulsar/issues/15966) It was actually discussed already very recently ((offline) that it's a good time to formally adopt it for the next release.
