Hi Lari, There are 5 open PRs https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+milestone%3A2.10.0 and #14225 is a release blocker. For #13376 and #13341, we are preparing the testing, to make sure they can safely ship to 2.10.0 For #10478, it's a critical fix for the current message redeliver which will impact the transaction correctness while using failover or exclusive subscription, and it has protocol changes, so we don't want to move it to 2.11 since the PR is done and already reviewed, just need more eyes on it.
And, for the new metadata API, we found an issue that will introduce the cache inconsistent issue, we are working on a fix, it should be a release blocker, otherwise, 2.10 will not able to use. Another one is related to https://github.com/apache/pulsar/pull/13383, we are doing more tests to make sure it will not introduce break changes. > Are we planning to follow this process, or is PIP 47 obsolete? I'm doing my best to follow PIP 47, but when seeing a potential break change, I need to confirm it. After all the potential break changes have been confirmed and fixed, I will start the vote thread. Thanks, Penghui On Mon, Feb 14, 2022 at 7:24 PM Lari Hotari <lhot...@apache.org> wrote: > > After the features are completed, I will create the new 2.10 branch, and > > only apply > > the critical bug fixes, regression fixes. So that we can have adequate > > testing on branch-2.10 > > Hi Penghui, > > What's the status of 2.10.0 release? What features aren't complete? > > In PIP 47 ( > https://github.com/apache/pulsar/wiki/PIP-47%3A-Time-Based-Release-Plan), > there's a high-level description of the Pulsar release process: > > "A month before the release date, the release manager will cut branches > and also publish (preferably on the wiki) a list of features that will be > included in the release (these will typically be PIPs, but not always). We > will leave another week for "minor" features to get in (see below for > definitions), but at this point we will start efforts to stabilize the > release branch and contribute mostly tests and fixes. Two weeks after > branch cutting, we will announce code-freeze and start rolling out RCs, > after which only fixes for blocking bugs will be merged." > > Are we planning to follow this process, or is PIP 47 obsolete? > > -Lari >
