Thanks all the Kafka contributors for voting! The vote passes with 6 binding +1, 5 non-binding +1 and no -1.
We are now 11 days before the first planned release candidate. We have 12 open blockers, 17 open critical issues and a grand total of 108 issues for the release. I added a widget showing the current issues for the release to the release tracking page (https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.0) Please take a look at the list. We need to be focused on getting all the high priority items resolved by March 21. You can contribute by fixing issues, by reviewing patches or by moving JIRAs to the next release (if you are the owner). Remember that community reviews are incredibly useful feedback to the developers, so don't hesitate to review even if you lack a commit bit. Gwen On Tue, Mar 8, 2016 at 8:35 AM, Grant Henke <ghe...@cloudera.com> wrote: > +1 (non-binding). > > I will review and update any jiras I think should be tracked today. > > Gwen the release tracking page is awesome! > +1 (non-binding) > > One clarification: there are currently 11 issues marked as blockers, is > that an accurate list? > > http://bit.ly/21YCthZ > > -Flavio > >> On 08 Mar 2016, at 06:12, Harsha <ka...@harsha.io> wrote: >> >> >> +1 >> >> Thanks, >> Harsha >> On Mon, Mar 7, 2016, at 09:49 PM, Jun Rao wrote: >>> +1 >>> >>> Thanks, >>> >>> Jun >>> >>> 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 >>>>
