Re: [VOTE] Release plan - Kafka 0.10.0

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

Re: [VOTE] Release plan - Kafka 0.10.0

+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

Re: [VOTE] Release plan - Kafka 0.10.0

For a certain definition of accurate :) We can add blockers as we find critical bugs and we can remove items if they become less relevant. As we get closer to rolling out the release candidate, we can re-evaluate the remaining blockers and re-consider whether they indeed prevent us from voting a

Re: [VOTE] Release plan - Kafka 0.10.0

+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 wrote: > > > +1 > > Thanks, > Harsha > On Mon, Mar 7, 2016, at 09:49 PM, Jun Rao wrote: >> +1

Re: [VOTE] Release plan - Kafka 0.10.0

+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 wrote: > > > Greetings Kafka Developer Community, > > > > As you all know, we have few big features that are almost complete > >

Re: [VOTE] Release plan - Kafka 0.10.0

+1 Thanks, Jun On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira 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

Re: [VOTE] Release plan - Kafka 0.10.0

I added a section on "how to contribute to the release" to the release plan: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.0 Please help out! :) On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira wrote: > Greetings Kafka Developer Community, > > As you all

Re: [VOTE] Release plan - Kafka 0.10.0

Perfect! Missed out those JIRAs. They should cover the concern. On Mon, Mar 7, 2016 at 5:21 PM, Gwen Shapira wrote: > We are planning on supporting 0.8.2 upgrades too. > > We already have KAFKA-3188 and KAFKA-3201 for the tests. Do you think > they are incomplete? > > On Mon,

Re: [VOTE] Release plan - Kafka 0.10.0

We are planning on supporting 0.8.2 upgrades too. We already have KAFKA-3188 and KAFKA-3201 for the tests. Do you think they are incomplete? On Mon, Mar 7, 2016 at 5:15 PM, Ashish Singh wrote: > +1 (non-binding) > > My understanding is that we decided to support upgrading

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (non-binding) My understanding is that we decided to support upgrading from 08.2.x to 0.10.0.0 as well, due to short release cycle. Please correct me if that is not true. Created KAFKA-3348 and KAFKA-3349 to add tests for making sure following paths work fine. 1. 0.8.2.x -> 0.10.0.0 2.

Re: [VOTE] Release plan - Kafka 0.10.0

Important clarification: In order to keep the release quality up to the usual Kafka standards, we will want to only commit tested features. When deciding on whether to push your feature into 0.10.0 or delay to the next release, please take into account whether you'll have time to complete the

Re: [VOTE] Release plan - Kafka 0.10.0

In order to track the many KIPs that we are trying to land in the next two weeks, I created this page: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.0 There are a lot of KIPs under discussion and not too much time to finalize all of them. Lets do our best to review, discuss

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (non-binding) BTW, if possible, I would like to have KIP-33 in 0.10.0 to solve the long pending retention issue. On Mon, Mar 7, 2016 at 3:26 PM, Joel Koshy wrote: > +1 > > On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira wrote: > > > Greetings Kafka

Re: [VOTE] Release plan - Kafka 0.10.0

+1 On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira 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

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (non-binding) Ismael On Mon, Mar 7, 2016 at 7:27 PM, Neha Narkhede wrote: > +1 (binding) > > On Mon, Mar 7, 2016 at 11:26 AM, Gwen Shapira wrote: > > > Hi Joe, > > > > The branch cutting means that new features will go into trunk, bug > > fixes will go

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (binding) On Mon, Mar 7, 2016 at 11:26 AM, Gwen Shapira wrote: > Hi Joe, > > The branch cutting means that new features will go into trunk, bug > fixes will go into either trunk and branch or just trunk - depending > on committer decision. Committers should take into

Re: [VOTE] Release plan - Kafka 0.10.0

Hi Joe, The branch cutting means that new features will go into trunk, bug fixes will go into either trunk and branch or just trunk - depending on committer decision. Committers should take into consideration the importance of the fix vs the stability of the planned release. I don't have specific

Re: [VOTE] Release plan - Kafka 0.10.0

+1 On Mon, Mar 7, 2016 at 9:42 AM, Joe Stein wrote: > +1 > > quick question/definition for the release cut (assuming vote passes) your > proposing please. > > Critical bug fixes for new features and regression or just regression and > new feature can get pulled if not

Re: [VOTE] Release plan - Kafka 0.10.0

+1 quick question/definition for the release cut (assuming vote passes) your proposing please. Critical bug fixes for new features and regression or just regression and new feature can get pulled if not working right if less impactful to-do so? Understandably that is dependent on the feature

[VOTE] Release plan - Kafka 0.10.0

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 *