Re: [VOTE] Release plan - Kafka 0.10.0

[Gwen Shapira]

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  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  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  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

Re: [VOTE] Release plan - Kafka 0.10.0

[Grant Henke]

+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  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  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
>>>

Re: [VOTE] Release plan - Kafka 0.10.0

[Gwen Shapira]

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 release.

If you want to discuss anything specific, we can do so on the relevant JIRA.

Gwen

On Tue, Mar 8, 2016 at 1:45 AM, Flavio Junqueira  wrote:
> +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
>>>
>>> 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 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

>

Re: [VOTE] Release plan - Kafka 0.10.0

[Flavio Junqueira]

+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
>> 
>> 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 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
>>> 

Re: [VOTE] Release plan - Kafka 0.10.0

[Harsha]

+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
> > (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
> >

Re: [VOTE] Release plan - Kafka 0.10.0

[Jun Rao]

+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 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
>

Re: [VOTE] Release plan - Kafka 0.10.0

[Gwen Shapira]

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 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

Re: [VOTE] Release plan - Kafka 0.10.0

[Ashish Singh]

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, Mar 7, 2016 at 5:15 PM, Ashish Singh  wrote:
> > +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. 0.9.1.x -> 0.10.0.0
> >
> >
> > On Mon, Mar 7, 2016 at 5:04 PM, Gwen Shapira  wrote:
> >
> >> 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 system tests for the feature and not just the basic code.
> >>
> >> Gwen
> >>
> >> On Mon, Mar 7, 2016 at 4:53 PM, Gwen Shapira  wrote:
> >> > 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 and vote on
> >> > the KIPs, so the developers will have a chance of getting a patch in
> >> > on time.
> >> >
> >> > Gwen
> >> >
> >> > On Mon, Mar 7, 2016 at 4:46 PM, Becket Qin 
> wrote:
> >> >> +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 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
> >> >>> >
> >> >>>
> >>
> >
> >
> >
> > --
> >
> > Regards,
> > Ashish
>



-- 

Regards,
Ashish

Re: [VOTE] Release plan - Kafka 0.10.0

[Gwen Shapira]

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 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. 0.9.1.x -> 0.10.0.0
>
>
> On Mon, Mar 7, 2016 at 5:04 PM, Gwen Shapira  wrote:
>
>> 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 system tests for the feature and not just the basic code.
>>
>> Gwen
>>
>> On Mon, Mar 7, 2016 at 4:53 PM, Gwen Shapira  wrote:
>> > 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 and vote on
>> > the KIPs, so the developers will have a chance of getting a patch in
>> > on time.
>> >
>> > Gwen
>> >
>> > On Mon, Mar 7, 2016 at 4:46 PM, Becket Qin  wrote:
>> >> +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 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
>> >>> >
>> >>>
>>
>
>
>
> --
>
> Regards,
> Ashish

Re: [VOTE] Release plan - Kafka 0.10.0

[Ashish Singh]

+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. 0.9.1.x -> 0.10.0.0


On Mon, Mar 7, 2016 at 5:04 PM, Gwen Shapira  wrote:

> 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 system tests for the feature and not just the basic code.
>
> Gwen
>
> On Mon, Mar 7, 2016 at 4:53 PM, Gwen Shapira  wrote:
> > 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 and vote on
> > the KIPs, so the developers will have a chance of getting a patch in
> > on time.
> >
> > Gwen
> >
> > On Mon, Mar 7, 2016 at 4:46 PM, Becket Qin  wrote:
> >> +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 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
> >>> >
> >>>
>



-- 

Regards,
Ashish

Re: [VOTE] Release plan - Kafka 0.10.0

[Gwen Shapira]

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 system tests for the feature and not just the basic code.

Gwen

On Mon, Mar 7, 2016 at 4:53 PM, Gwen Shapira  wrote:
> 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 and vote on
> the KIPs, so the developers will have a chance of getting a patch in
> on time.
>
> Gwen
>
> On Mon, Mar 7, 2016 at 4:46 PM, Becket Qin  wrote:
>> +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 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
>>> >
>>>

Re: [VOTE] Release plan - Kafka 0.10.0

[Gwen Shapira]

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 and vote on
the KIPs, so the developers will have a chance of getting a patch in
on time.

Gwen

On Mon, Mar 7, 2016 at 4:46 PM, Becket Qin  wrote:
> +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 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
>> >
>>

Re: [VOTE] Release plan - Kafka 0.10.0

[Becket Qin]

+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 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
> >
>

Re: [VOTE] Release plan - Kafka 0.10.0

[Joel Koshy]

+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 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
>

Re: [VOTE] Release plan - Kafka 0.10.0

[Ismael Juma]

+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 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 rules in mind - our committers have excellent judgement
> > :)
> >
> > I hope this clarifies?
> >
> > Gwen
> >
> >
> >
> > 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 working right if less impactful to-do
> > so?
> > > Understandably that is dependent on the feature and/or fix but we have
> a
> > > bunch on the plan for
> > > https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan
> > and
> > > is that the hard freeze? I think the producer and consumer interceptors
> > are
> > > part of streams so maybe just an update on that?
> > >
> > > +1 the timeline seems manageable and adjusting for what is released or
> > not
> > > doesn't affect the approach so g2g lots to get out
> > >
> > > for 0.11 I would like to suggest trying to nominate or if volunteer
> > always
> > > good a release manager along with what is being worked on and
> collaborate
> > > around for different KIP so folks know where to contribute and work
> > > downstream too operational.
> > >
> > > ~ Joe Stein
> > >
> > > On Mon, Mar 7, 2016 at 12:27 PM, 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 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
> > >>
> >
>
>
>
> --
> Thanks,
> Neha
>

Re: [VOTE] Release plan - Kafka 0.10.0

[Neha Narkhede]

+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 consideration the
> importance of the fix vs the stability of the planned release. I don't
> have specific rules in mind - our committers have excellent judgement
> :)
>
> I hope this clarifies?
>
> Gwen
>
>
>
> 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 working right if less impactful to-do
> so?
> > Understandably that is dependent on the feature and/or fix but we have a
> > bunch on the plan for
> > https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan
> and
> > is that the hard freeze? I think the producer and consumer interceptors
> are
> > part of streams so maybe just an update on that?
> >
> > +1 the timeline seems manageable and adjusting for what is released or
> not
> > doesn't affect the approach so g2g lots to get out
> >
> > for 0.11 I would like to suggest trying to nominate or if volunteer
> always
> > good a release manager along with what is being worked on and collaborate
> > around for different KIP so folks know where to contribute and work
> > downstream too operational.
> >
> > ~ Joe Stein
> >
> > On Mon, Mar 7, 2016 at 12:27 PM, 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 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
> >>
>



-- 
Thanks,
Neha

Re: [VOTE] Release plan - Kafka 0.10.0

[Gwen Shapira]

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 rules in mind - our committers have excellent judgement
:)

I hope this clarifies?

Gwen



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 working right if less impactful to-do so?
> Understandably that is dependent on the feature and/or fix but we have a
> bunch on the plan for
> https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan and
> is that the hard freeze? I think the producer and consumer interceptors are
> part of streams so maybe just an update on that?
>
> +1 the timeline seems manageable and adjusting for what is released or not
> doesn't affect the approach so g2g lots to get out
>
> for 0.11 I would like to suggest trying to nominate or if volunteer always
> good a release manager along with what is being worked on and collaborate
> around for different KIP so folks know where to contribute and work
> downstream too operational.
>
> ~ Joe Stein
>
> On Mon, Mar 7, 2016 at 12:27 PM, 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 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
>>

Re: [VOTE] Release plan - Kafka 0.10.0

[Ewen Cheslack-Postava]

+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 working right if less impactful to-do so?
> Understandably that is dependent on the feature and/or fix but we have a
> bunch on the plan for
> https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan and
> is that the hard freeze? I think the producer and consumer interceptors are
> part of streams so maybe just an update on that?
>
> +1 the timeline seems manageable and adjusting for what is released or not
> doesn't affect the approach so g2g lots to get out
>
> for 0.11 I would like to suggest trying to nominate or if volunteer always
> good a release manager along with what is being worked on and collaborate
> around for different KIP so folks know where to contribute and work
> downstream too operational.
>
> ~ Joe Stein
>
> On Mon, Mar 7, 2016 at 12:27 PM, 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 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
> >
>



-- 
Thanks,
Ewen

Re: [VOTE] Release plan - Kafka 0.10.0

[Joe Stein]

+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 and/or fix but we have a
bunch on the plan for
https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan and
is that the hard freeze? I think the producer and consumer interceptors are
part of streams so maybe just an update on that?

+1 the timeline seems manageable and adjusting for what is released or not
doesn't affect the approach so g2g lots to get out

for 0.11 I would like to suggest trying to nominate or if volunteer always
good a release manager along with what is being worked on and collaborate
around for different KIP so folks know where to contribute and work
downstream too operational.

~ Joe Stein

On Mon, Mar 7, 2016 at 12:27 PM, 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 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
>

[VOTE] Release plan - Kafka 0.10.0

[Gwen Shapira]

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