Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

[Becket Qin]

Hi Ismael,

I was trying to see what people think here. I will create an official
[VOTE] thread.

Thanks,

Jiangjie (Becket) Qin

On Thu, Feb 18, 2016 at 6:14 AM, Tom Graves 
wrote:

> +1
> Tom
>
> On Tuesday, February 9, 2016 12:08 PM, Becket Qin <
> becket@gmail.com> wrote:
>
>
>  Hi All,
>
> Next Kafka release will have several significant important new
> feature/changes such as Kafka Stream, Message Format Change, Client
> Interceptors and several new consumer API changes, etc. We feel it is
> better to make next Kafka release 0.10.0.0 instead of 0.9.1.0.
>
> We would like to see what do people think of making the next release
> 0.10.0.0.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>
>
>
>

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

[Tom Graves]

+1
Tom 

On Tuesday, February 9, 2016 12:08 PM, Becket Qin  
wrote:
 

 Hi All,

Next Kafka release will have several significant important new
feature/changes such as Kafka Stream, Message Format Change, Client
Interceptors and several new consumer API changes, etc. We feel it is
better to make next Kafka release 0.10.0.0 instead of 0.9.1.0.

We would like to see what do people think of making the next release
0.10.0.0.

Thanks,

Jiangjie (Becket) Qin


   

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

[Ismael Juma]

Hi Becket,

Did you mean this to be an official [VOTE] thread? If so, it may be a good
idea to start a new thread with the appropriate title and link to this one.
It would be good to agree on this relatively soon so that we can update
JIRA, the wiki and anywhere in the code and documentation where we
reference the version number.

Ismael

On Wed, Feb 10, 2016 at 1:33 AM, Ismael Juma  wrote:

> Hi Becket,
>
> Good points. Some comments inline.
>
> On Tue, Feb 9, 2016 at 8:45 PM, Becket Qin  wrote:
>
>> Good point on the upgrade path. The release plan says that 0.10.0.0 is
>> targeted in Q2, 2016. If that is accurate, there are 6-7 months between
>> 0.9.0.0 and 0.10.0.0, i.e. there are still about five months before the
>> next release.
>
>
> I am not sure how accurate that release plan[1] is since it was last
> updated in September 2015 (before 0.9.0.0 was released).
> For comparison, Kafka 0.7.0 was released in January 2012, 0.8.0 in
> December 2013 (almost two years later), 0.9.0.0 in November 2015 (almost
> two years later). It is likely that this will be the fastest major release
> bump by far. It is not necessarily an issue, but we should take special
> care to help users.
>
> Our previous documentation only provides documentation on how
>> to upgrade from the last official release. If the releasing interval is a
>> concern, we can add documentation on how to upgrade from 0.8.x to 0.10.0.0
>> directly. Alternatively, we can suggest user to first upgrade to 0.9.0.0
>> then upgrade to 0.10.0.0.
>
>
> These are the options indeed. If there is an upgrade path from 0.8.2.x to
> 0.10.0.0 that is simpler than having to upgrade to 0.9.0.x first, I think
> it would be valuable to document it as our users would appreciate it. This
> is obviously more work (we would want to write ducktape tests to ensure
> that the documentation steps actually work as we expect) and it potentially
> introduces new failure scenarios. I'd be interested in what others think.
>
> Ismael
>
> [1] https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan
>

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

[Ismael Juma]

Hi Becket,

Thanks for starting the discussion.

Given the significance of the changes, I think 0.10.0.0 is appropriate.

However, I think we have to be careful about the fact that we will be
releasing two major releases within a short period of time. This means that
0.10.0.0 may be out before many have have upgraded to 0.9.0.x. It would be
good to understand the upgrade path for such people. Finally, we should be
very clear about what the version number means in terms of compatibility.
Some people were confused by the significance of the 0.8.3.0 to 0.9.0.0
rename.

Ismael

On Tue, Feb 9, 2016 at 6:07 PM, Becket Qin  wrote:

> Hi All,
>
> Next Kafka release will have several significant important new
> feature/changes such as Kafka Stream, Message Format Change, Client
> Interceptors and several new consumer API changes, etc. We feel it is
> better to make next Kafka release 0.10.0.0 instead of 0.9.1.0.
>
> We would like to see what do people think of making the next release
> 0.10.0.0.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

[Becket Qin]

Hi Ismael,

Good point on the upgrade path. The release plan says that 0.10.0.0 is
targeted in Q2, 2016. If that is accurate, there are 6-7 months between
0.9.0.0 and 0.10.0.0, i.e. there are still about five months before the
next release. Our previous documentation only provides documentation on how
to upgrade from the last official release. If the releasing interval is a
concern, we can add documentation on how to upgrade from 0.8.x to 0.10.0.0
directly. Alternatively, we can suggest user to first upgrade to 0.9.0.0
then upgrade to 0.10.0.0.

Compatibility wise, personally I think a major version bump implies there
can be some backward incompatible change and people have to read upgrade
instructions before upgrade. We need to make it very clear in our upgrade
documentation like we did for 0.9.0.0.

Regarding the version renaming, actually I was one the people who was
confused about 0.8.3 to 0.9.0.0 rename. My take from last rename is that if
we have significant new features added, a new major release is preferred.
This is the same rationale behind this poll. The significance might be a
little subjective, but somehow people seem to have similar threshold on
that. :)

Thanks,

Jiangjie (Becket) Qin


On Tue, Feb 9, 2016 at 10:43 AM, Ismael Juma  wrote:

> Hi Becket,
>
> Thanks for starting the discussion.
>
> Given the significance of the changes, I think 0.10.0.0 is appropriate.
>
> However, I think we have to be careful about the fact that we will be
> releasing two major releases within a short period of time. This means that
> 0.10.0.0 may be out before many have have upgraded to 0.9.0.x. It would be
> good to understand the upgrade path for such people. Finally, we should be
> very clear about what the version number means in terms of compatibility.
> Some people were confused by the significance of the 0.8.3.0 to 0.9.0.0
> rename.
>
> Ismael
>
> On Tue, Feb 9, 2016 at 6:07 PM, Becket Qin  wrote:
>
> > Hi All,
> >
> > Next Kafka release will have several significant important new
> > feature/changes such as Kafka Stream, Message Format Change, Client
> > Interceptors and several new consumer API changes, etc. We feel it is
> > better to make next Kafka release 0.10.0.0 instead of 0.9.1.0.
> >
> > We would like to see what do people think of making the next release
> > 0.10.0.0.
> >
> > Thanks,
> >
> > Jiangjie (Becket) Qin
> >
>

[POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

[Becket Qin]

Hi All,

Next Kafka release will have several significant important new
feature/changes such as Kafka Stream, Message Format Change, Client
Interceptors and several new consumer API changes, etc. We feel it is
better to make next Kafka release 0.10.0.0 instead of 0.9.1.0.

We would like to see what do people think of making the next release
0.10.0.0.

Thanks,

Jiangjie (Becket) Qin

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

[Stevo Slavić]

+1 0.10.0.0

On Tue, Feb 9, 2016, 19:08 Becket Qin  wrote:

> Hi All,
>
> Next Kafka release will have several significant important new
> feature/changes such as Kafka Stream, Message Format Change, Client
> Interceptors and several new consumer API changes, etc. We feel it is
> better to make next Kafka release 0.10.0.0 instead of 0.9.1.0.
>
> We would like to see what do people think of making the next release
> 0.10.0.0.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

[Neha Narkhede]

+1 on 0.10.0.0

On Tue, Feb 9, 2016 at 10:09 AM, Stevo Slavić  wrote:

> +1 0.10.0.0
>
> On Tue, Feb 9, 2016, 19:08 Becket Qin  wrote:
>
> > Hi All,
> >
> > Next Kafka release will have several significant important new
> > feature/changes such as Kafka Stream, Message Format Change, Client
> > Interceptors and several new consumer API changes, etc. We feel it is
> > better to make next Kafka release 0.10.0.0 instead of 0.9.1.0.
> >
> > We would like to see what do people think of making the next release
> > 0.10.0.0.
> >
> > Thanks,
> >
> > Jiangjie (Becket) Qin
> >
>



-- 
Thanks,
Neha

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

[Gwen Shapira]

sure, why not :)

On Tue, Feb 9, 2016 at 10:07 AM, Becket Qin  wrote:

> Hi All,
>
> Next Kafka release will have several significant important new
> feature/changes such as Kafka Stream, Message Format Change, Client
> Interceptors and several new consumer API changes, etc. We feel it is
> better to make next Kafka release 0.10.0.0 instead of 0.9.1.0.
>
> We would like to see what do people think of making the next release
> 0.10.0.0.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

[Ismael Juma]

Hi Becket,

Good points. Some comments inline.

On Tue, Feb 9, 2016 at 8:45 PM, Becket Qin  wrote:

> Good point on the upgrade path. The release plan says that 0.10.0.0 is
> targeted in Q2, 2016. If that is accurate, there are 6-7 months between
> 0.9.0.0 and 0.10.0.0, i.e. there are still about five months before the
> next release.


I am not sure how accurate that release plan[1] is since it was last
updated in September 2015 (before 0.9.0.0 was released).
For comparison, Kafka 0.7.0 was released in January 2012, 0.8.0 in December
2013 (almost two years later), 0.9.0.0 in November 2015 (almost two years
later). It is likely that this will be the fastest major release bump by
far. It is not necessarily an issue, but we should take special care to
help users.

Our previous documentation only provides documentation on how
> to upgrade from the last official release. If the releasing interval is a
> concern, we can add documentation on how to upgrade from 0.8.x to 0.10.0.0
> directly. Alternatively, we can suggest user to first upgrade to 0.9.0.0
> then upgrade to 0.10.0.0.


These are the options indeed. If there is an upgrade path from 0.8.2.x to
0.10.0.0 that is simpler than having to upgrade to 0.9.0.x first, I think
it would be valuable to document it as our users would appreciate it. This
is obviously more work (we would want to write ducktape tests to ensure
that the documentation steps actually work as we expect) and it potentially
introduces new failure scenarios. I'd be interested in what others think.

Ismael

[1] https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan