Status

Current state: Under DiscussionAccepted

Discussion thread: N/A http://mail-archives.apache.org/mod_mbox/bookkeeper-dev/201708.mbox/%3CCAO2yDyZbJwqATZb12vL9fN8VcTi7MxGconoiACxO4QNoqpYVzw%40mail.gmail.com%3E

JIRA:  NN/A

Released:  N/AStarting from 4.6.0

This proposal is to adopt Kafka's Time Based Release Plan.

...

At this stage we are planning to make a release every 4 3 month.

• 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 BPs, 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.

...

If we switched to Time based release plan, we will have more releases. We need to define an EOL Policy. Given 3 4 releases a year and the fact that no one upgrades three times a year, we propose making sure (by testing!) that rolling upgrade can be done from each release in the past year (i.e. last 3 4 releases) to the latest version.

We will also attempt, as a community to do bugfix releases as needed for the last 3 releases4 releases.

Who Manages The Releases?

...