> 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

Reply via email to