+1 On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira <g...@confluent.io> wrote:
> Greetings Kafka Developer Community, > > As you all know, we have few big features that are almost complete > (Timestamps! Interceptors! Streams!). It is time to start planning our > next release. > > I suggest the following: > * Cut branches on March 21st > * Publish the first release candidate the next day > * Start testing, finding important issues, fixing them, rolling out new > releases > * And eventually get a release candidate that we all agree is awesome > enough to release. Hopefully this won't take too many iterations :) > > Note that this is a 2 weeks heads-up on branch cutting. After we cut > branches, we will try to minimize cherrypicks to just critical bugs > (because last major release was a bit insane). > Therefore, if you have a feature that you really want to see in > 0.10.0 - you'll need to have it committed by March 21st. As a curtesy > to the release manager, if you have features that you are not planning > on getting in for 0.10.0, please change the "fix version" field in > JIRA accordingly. > > I will send a heads-up few days before cutting branches, to give > everyone a chance to get stragglers in. > > The vote will be open for 72 hours. > All in favor, please reply with +1. > > Gwen Shapira >
