You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Joe Stein <jo...@stealth.ly> on 2014/09/30 18:53:04 UTC

[DISCUSS] 0.8.1.2 Release

Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.

Here are the JIRAs I would like to propose to back port a patch (if not
already done so) and apply them to the 0.8.1 branch for a 0.8.1.2 release

https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for scala
2.11)
https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on
partition state update failures)
https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew initial
setup output from source distribution)
https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in our src
release)

If the community and committers can comment on the patches proposed that
would be great. If I missed any bring them up or if you think any I have
proposed shouldn't be int he release bring that up too please.

Once we have consensus on this thread my thought was that I would apply and
commit the agreed to tickets to the 0.8.1 branch. If any tickets don't
apply of course a back port patch has to happen through our standard
process (not worried about that we have some engineering cycles to
contribute to making that happen). Once that is all done, I will build
0.8.1.2 release artifacts and call a VOTE for RC1.

/*******************************************
 Joe Stein
 Founder, Principal Consultant
 Big Data Open Source Security LLC
 http://www.stealth.ly
 Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
********************************************/

RE: [DISCUSS] 0.8.1.2 Release

Posted by "Seshadri, Balaji" <Ba...@dish.com>.
In DISH we are having issues in 0.8-beta version used in PROD, it's crashing every 2 days and becoming a blocker for us.

It would be great if we get 0.8.2 or 0.8.1.2 whichever is faster as we can't wait for 3 weeks as our new Order Management system is going to sit on top of Kafka.

-----Original Message-----
From: Neha Narkhede [mailto:neha.narkhede@gmail.com] 
Sent: Tuesday, September 30, 2014 1:37 PM
To: users@kafka.apache.org
Cc: dev@kafka.apache.org
Subject: Re: [DISCUSS] 0.8.1.2 Release

Can we discuss the need for 0.8.1.2? I'm wondering if it's related to the timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in the next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just upgrade to 0.8.2?

On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly> wrote:

> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
>
> Here are the JIRAs I would like to propose to back port a patch (if 
> not already done so) and apply them to the 0.8.1 branch for a 0.8.1.2 
> release
>
> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for 
> scala
> 2.11)
> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on 
> partition state update failures)
> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew 
> initial setup output from source distribution)
> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in 
> our src
> release)
>
> If the community and committers can comment on the patches proposed 
> that would be great. If I missed any bring them up or if you think any 
> I have proposed shouldn't be int he release bring that up too please.
>
> Once we have consensus on this thread my thought was that I would 
> apply and commit the agreed to tickets to the 0.8.1 branch. If any 
> tickets don't apply of course a back port patch has to happen through 
> our standard process (not worried about that we have some engineering 
> cycles to contribute to making that happen). Once that is all done, I 
> will build
> 0.8.1.2 release artifacts and call a VOTE for RC1.
>
> /*******************************************
>  Joe Stein
>  Founder, Principal Consultant
>  Big Data Open Source Security LLC
>  http://www.stealth.ly
>  Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> ********************************************/
>

Re: [DISCUSS] 0.8.1.2 Release

Posted by Jun Rao <ju...@gmail.com>.
Balaji,

Thanks for your interest. Do you think you could help on KAFKA-1493?

Jun

On Thu, Oct 2, 2014 at 3:17 PM, Seshadri, Balaji <Ba...@dish.com>
wrote:

> I would be glad to help in any of these blockers,please let me know.
>
> Thanks,
>
> Balaji
>
> -----Original Message-----
> From: Jun Rao [mailto:junrao@gmail.com]
> Sent: Thursday, October 02, 2014 3:48 PM
> To: users@kafka.apache.org
> Cc: dev@kafka.apache.org
> Subject: Re: [DISCUSS] 0.8.1.2 Release
>
> We already cut an 0.8.2 release branch. The plan is to have the remaining
> blockers resolved before releasing it. Hopefully this will just take a
> couple of weeks.
>
>
> https://issues.apache.org/jira/browse/KAFKA-1663?filter=-4&jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20priority%20%3D%20Blocker%20AND%20fixVersion%20%3D%200.8.2%20ORDER%20BY%20createdDate%20DESC
>
> Thanks,
>
> Jun
>
> On Thu, Oct 2, 2014 at 11:28 AM, Kane Kane <ka...@gmail.com> wrote:
>
> > Having the same question: what happened to 0.8.2 release, when it's
> > supposed to happen?
> >
> > Thanks.
> >
> > On Tue, Sep 30, 2014 at 12:49 PM, Jonathan Weeks
> > <jo...@gmail.com> wrote:
> > > I was one asking for 0.8.1.2 a few weeks back, when 0.8.2 was at
> > > least
> > 6-8 weeks out.
> > >
> > > If we truly believe that 0.8.2 will go “golden” and stable in 2-3
> > > weeks,
> > I, for one, don’t need a 0.8.1.2, but it depends on the confidence in
> > shipping 0.8.2 soonish.
> > >
> > > YMMV,
> > >
> > > -Jonathan
> > >
> > >
> > > On Sep 30, 2014, at 12:37 PM, Neha Narkhede
> > > <ne...@gmail.com>
> > wrote:
> > >
> > >> Can we discuss the need for 0.8.1.2? I'm wondering if it's related
> > >> to
> > the
> > >> timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out
> > >> in
> > the
> > >> next 2-3 weeks, do we still need to get 0.8.1.2 out or can people
> > >> just upgrade to 0.8.2?
> > >>
> > >> On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly>
> > wrote:
> > >>
> > >>> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
> > >>>
> > >>> Here are the JIRAs I would like to propose to back port a patch
> > >>> (if not already done so) and apply them to the 0.8.1 branch for a
> > >>> 0.8.1.2
> > release
> > >>>
> > >>> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is
> > >>> empty)
> > >>> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for
> > scala
> > >>> 2.11)
> > >>> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion
> > >>> on partition state update failures)
> > >>> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew
> > initial
> > >>> setup output from source distribution)
> > >>> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars
> > >>> in
> > our
> > >>> src
> > >>> release)
> > >>>
> > >>> If the community and committers can comment on the patches
> > >>> proposed
> > that
> > >>> would be great. If I missed any bring them up or if you think any
> > >>> I
> > have
> > >>> proposed shouldn't be int he release bring that up too please.
> > >>>
> > >>> Once we have consensus on this thread my thought was that I would
> > apply and
> > >>> commit the agreed to tickets to the 0.8.1 branch. If any tickets
> > >>> don't apply of course a back port patch has to happen through our
> > >>> standard process (not worried about that we have some engineering
> > >>> cycles to contribute to making that happen). Once that is all
> > >>> done, I will build
> > >>> 0.8.1.2 release artifacts and call a VOTE for RC1.
> > >>>
> > >>> /*******************************************
> > >>> Joe Stein
> > >>> Founder, Principal Consultant
> > >>> Big Data Open Source Security LLC
> > >>> http://www.stealth.ly
> > >>> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> > >>> ********************************************/
> > >>>
> > >
> >
>

RE: [DISCUSS] 0.8.1.2 Release

Posted by "Seshadri, Balaji" <Ba...@dish.com>.
I would be glad to help in any of these blockers,please let me know.

Thanks,

Balaji

-----Original Message-----
From: Jun Rao [mailto:junrao@gmail.com] 
Sent: Thursday, October 02, 2014 3:48 PM
To: users@kafka.apache.org
Cc: dev@kafka.apache.org
Subject: Re: [DISCUSS] 0.8.1.2 Release

We already cut an 0.8.2 release branch. The plan is to have the remaining blockers resolved before releasing it. Hopefully this will just take a couple of weeks.

https://issues.apache.org/jira/browse/KAFKA-1663?filter=-4&jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20priority%20%3D%20Blocker%20AND%20fixVersion%20%3D%200.8.2%20ORDER%20BY%20createdDate%20DESC

Thanks,

Jun

On Thu, Oct 2, 2014 at 11:28 AM, Kane Kane <ka...@gmail.com> wrote:

> Having the same question: what happened to 0.8.2 release, when it's 
> supposed to happen?
>
> Thanks.
>
> On Tue, Sep 30, 2014 at 12:49 PM, Jonathan Weeks 
> <jo...@gmail.com> wrote:
> > I was one asking for 0.8.1.2 a few weeks back, when 0.8.2 was at 
> > least
> 6-8 weeks out.
> >
> > If we truly believe that 0.8.2 will go “golden” and stable in 2-3 
> > weeks,
> I, for one, don’t need a 0.8.1.2, but it depends on the confidence in 
> shipping 0.8.2 soonish.
> >
> > YMMV,
> >
> > -Jonathan
> >
> >
> > On Sep 30, 2014, at 12:37 PM, Neha Narkhede 
> > <ne...@gmail.com>
> wrote:
> >
> >> Can we discuss the need for 0.8.1.2? I'm wondering if it's related 
> >> to
> the
> >> timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out 
> >> in
> the
> >> next 2-3 weeks, do we still need to get 0.8.1.2 out or can people 
> >> just upgrade to 0.8.2?
> >>
> >> On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly>
> wrote:
> >>
> >>> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
> >>>
> >>> Here are the JIRAs I would like to propose to back port a patch 
> >>> (if not already done so) and apply them to the 0.8.1 branch for a 
> >>> 0.8.1.2
> release
> >>>
> >>> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is 
> >>> empty)
> >>> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for
> scala
> >>> 2.11)
> >>> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion 
> >>> on partition state update failures)
> >>> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew
> initial
> >>> setup output from source distribution)
> >>> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars 
> >>> in
> our
> >>> src
> >>> release)
> >>>
> >>> If the community and committers can comment on the patches 
> >>> proposed
> that
> >>> would be great. If I missed any bring them up or if you think any 
> >>> I
> have
> >>> proposed shouldn't be int he release bring that up too please.
> >>>
> >>> Once we have consensus on this thread my thought was that I would
> apply and
> >>> commit the agreed to tickets to the 0.8.1 branch. If any tickets 
> >>> don't apply of course a back port patch has to happen through our 
> >>> standard process (not worried about that we have some engineering 
> >>> cycles to contribute to making that happen). Once that is all 
> >>> done, I will build
> >>> 0.8.1.2 release artifacts and call a VOTE for RC1.
> >>>
> >>> /*******************************************
> >>> Joe Stein
> >>> Founder, Principal Consultant
> >>> Big Data Open Source Security LLC
> >>> http://www.stealth.ly
> >>> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> >>> ********************************************/
> >>>
> >
>

Re: [DISCUSS] 0.8.1.2 Release

Posted by Jun Rao <ju...@gmail.com>.
We already cut an 0.8.2 release branch. The plan is to have the remaining
blockers resolved before releasing it. Hopefully this will just take a
couple of weeks.

https://issues.apache.org/jira/browse/KAFKA-1663?filter=-4&jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20priority%20%3D%20Blocker%20AND%20fixVersion%20%3D%200.8.2%20ORDER%20BY%20createdDate%20DESC

Thanks,

Jun

On Thu, Oct 2, 2014 at 11:28 AM, Kane Kane <ka...@gmail.com> wrote:

> Having the same question: what happened to 0.8.2 release, when it's
> supposed to happen?
>
> Thanks.
>
> On Tue, Sep 30, 2014 at 12:49 PM, Jonathan Weeks
> <jo...@gmail.com> wrote:
> > I was one asking for 0.8.1.2 a few weeks back, when 0.8.2 was at least
> 6-8 weeks out.
> >
> > If we truly believe that 0.8.2 will go “golden” and stable in 2-3 weeks,
> I, for one, don’t need a 0.8.1.2, but it depends on the confidence in
> shipping 0.8.2 soonish.
> >
> > YMMV,
> >
> > -Jonathan
> >
> >
> > On Sep 30, 2014, at 12:37 PM, Neha Narkhede <ne...@gmail.com>
> wrote:
> >
> >> Can we discuss the need for 0.8.1.2? I'm wondering if it's related to
> the
> >> timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in
> the
> >> next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just
> >> upgrade to 0.8.2?
> >>
> >> On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly>
> wrote:
> >>
> >>> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
> >>>
> >>> Here are the JIRAs I would like to propose to back port a patch (if not
> >>> already done so) and apply them to the 0.8.1 branch for a 0.8.1.2
> release
> >>>
> >>> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
> >>> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for
> scala
> >>> 2.11)
> >>> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on
> >>> partition state update failures)
> >>> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew
> initial
> >>> setup output from source distribution)
> >>> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in
> our
> >>> src
> >>> release)
> >>>
> >>> If the community and committers can comment on the patches proposed
> that
> >>> would be great. If I missed any bring them up or if you think any I
> have
> >>> proposed shouldn't be int he release bring that up too please.
> >>>
> >>> Once we have consensus on this thread my thought was that I would
> apply and
> >>> commit the agreed to tickets to the 0.8.1 branch. If any tickets don't
> >>> apply of course a back port patch has to happen through our standard
> >>> process (not worried about that we have some engineering cycles to
> >>> contribute to making that happen). Once that is all done, I will build
> >>> 0.8.1.2 release artifacts and call a VOTE for RC1.
> >>>
> >>> /*******************************************
> >>> Joe Stein
> >>> Founder, Principal Consultant
> >>> Big Data Open Source Security LLC
> >>> http://www.stealth.ly
> >>> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> >>> ********************************************/
> >>>
> >
>

Re: [DISCUSS] 0.8.1.2 Release

Posted by Jun Rao <ju...@gmail.com>.
We already cut an 0.8.2 release branch. The plan is to have the remaining
blockers resolved before releasing it. Hopefully this will just take a
couple of weeks.

https://issues.apache.org/jira/browse/KAFKA-1663?filter=-4&jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20priority%20%3D%20Blocker%20AND%20fixVersion%20%3D%200.8.2%20ORDER%20BY%20createdDate%20DESC

Thanks,

Jun

On Thu, Oct 2, 2014 at 11:28 AM, Kane Kane <ka...@gmail.com> wrote:

> Having the same question: what happened to 0.8.2 release, when it's
> supposed to happen?
>
> Thanks.
>
> On Tue, Sep 30, 2014 at 12:49 PM, Jonathan Weeks
> <jo...@gmail.com> wrote:
> > I was one asking for 0.8.1.2 a few weeks back, when 0.8.2 was at least
> 6-8 weeks out.
> >
> > If we truly believe that 0.8.2 will go “golden” and stable in 2-3 weeks,
> I, for one, don’t need a 0.8.1.2, but it depends on the confidence in
> shipping 0.8.2 soonish.
> >
> > YMMV,
> >
> > -Jonathan
> >
> >
> > On Sep 30, 2014, at 12:37 PM, Neha Narkhede <ne...@gmail.com>
> wrote:
> >
> >> Can we discuss the need for 0.8.1.2? I'm wondering if it's related to
> the
> >> timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in
> the
> >> next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just
> >> upgrade to 0.8.2?
> >>
> >> On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly>
> wrote:
> >>
> >>> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
> >>>
> >>> Here are the JIRAs I would like to propose to back port a patch (if not
> >>> already done so) and apply them to the 0.8.1 branch for a 0.8.1.2
> release
> >>>
> >>> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
> >>> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for
> scala
> >>> 2.11)
> >>> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on
> >>> partition state update failures)
> >>> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew
> initial
> >>> setup output from source distribution)
> >>> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in
> our
> >>> src
> >>> release)
> >>>
> >>> If the community and committers can comment on the patches proposed
> that
> >>> would be great. If I missed any bring them up or if you think any I
> have
> >>> proposed shouldn't be int he release bring that up too please.
> >>>
> >>> Once we have consensus on this thread my thought was that I would
> apply and
> >>> commit the agreed to tickets to the 0.8.1 branch. If any tickets don't
> >>> apply of course a back port patch has to happen through our standard
> >>> process (not worried about that we have some engineering cycles to
> >>> contribute to making that happen). Once that is all done, I will build
> >>> 0.8.1.2 release artifacts and call a VOTE for RC1.
> >>>
> >>> /*******************************************
> >>> Joe Stein
> >>> Founder, Principal Consultant
> >>> Big Data Open Source Security LLC
> >>> http://www.stealth.ly
> >>> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> >>> ********************************************/
> >>>
> >
>

Re: [DISCUSS] 0.8.1.2 Release

Posted by Kane Kane <ka...@gmail.com>.
Having the same question: what happened to 0.8.2 release, when it's
supposed to happen?

Thanks.

On Tue, Sep 30, 2014 at 12:49 PM, Jonathan Weeks
<jo...@gmail.com> wrote:
> I was one asking for 0.8.1.2 a few weeks back, when 0.8.2 was at least 6-8 weeks out.
>
> If we truly believe that 0.8.2 will go “golden” and stable in 2-3 weeks, I, for one, don’t need a 0.8.1.2, but it depends on the confidence in shipping 0.8.2 soonish.
>
> YMMV,
>
> -Jonathan
>
>
> On Sep 30, 2014, at 12:37 PM, Neha Narkhede <ne...@gmail.com> wrote:
>
>> Can we discuss the need for 0.8.1.2? I'm wondering if it's related to the
>> timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in the
>> next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just
>> upgrade to 0.8.2?
>>
>> On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly> wrote:
>>
>>> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
>>>
>>> Here are the JIRAs I would like to propose to back port a patch (if not
>>> already done so) and apply them to the 0.8.1 branch for a 0.8.1.2 release
>>>
>>> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
>>> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for scala
>>> 2.11)
>>> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on
>>> partition state update failures)
>>> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew initial
>>> setup output from source distribution)
>>> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in our
>>> src
>>> release)
>>>
>>> If the community and committers can comment on the patches proposed that
>>> would be great. If I missed any bring them up or if you think any I have
>>> proposed shouldn't be int he release bring that up too please.
>>>
>>> Once we have consensus on this thread my thought was that I would apply and
>>> commit the agreed to tickets to the 0.8.1 branch. If any tickets don't
>>> apply of course a back port patch has to happen through our standard
>>> process (not worried about that we have some engineering cycles to
>>> contribute to making that happen). Once that is all done, I will build
>>> 0.8.1.2 release artifacts and call a VOTE for RC1.
>>>
>>> /*******************************************
>>> Joe Stein
>>> Founder, Principal Consultant
>>> Big Data Open Source Security LLC
>>> http://www.stealth.ly
>>> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
>>> ********************************************/
>>>
>

Re: [DISCUSS] 0.8.1.2 Release

Posted by Kane Kane <ka...@gmail.com>.
Having the same question: what happened to 0.8.2 release, when it's
supposed to happen?

Thanks.

On Tue, Sep 30, 2014 at 12:49 PM, Jonathan Weeks
<jo...@gmail.com> wrote:
> I was one asking for 0.8.1.2 a few weeks back, when 0.8.2 was at least 6-8 weeks out.
>
> If we truly believe that 0.8.2 will go “golden” and stable in 2-3 weeks, I, for one, don’t need a 0.8.1.2, but it depends on the confidence in shipping 0.8.2 soonish.
>
> YMMV,
>
> -Jonathan
>
>
> On Sep 30, 2014, at 12:37 PM, Neha Narkhede <ne...@gmail.com> wrote:
>
>> Can we discuss the need for 0.8.1.2? I'm wondering if it's related to the
>> timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in the
>> next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just
>> upgrade to 0.8.2?
>>
>> On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly> wrote:
>>
>>> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
>>>
>>> Here are the JIRAs I would like to propose to back port a patch (if not
>>> already done so) and apply them to the 0.8.1 branch for a 0.8.1.2 release
>>>
>>> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
>>> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for scala
>>> 2.11)
>>> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on
>>> partition state update failures)
>>> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew initial
>>> setup output from source distribution)
>>> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in our
>>> src
>>> release)
>>>
>>> If the community and committers can comment on the patches proposed that
>>> would be great. If I missed any bring them up or if you think any I have
>>> proposed shouldn't be int he release bring that up too please.
>>>
>>> Once we have consensus on this thread my thought was that I would apply and
>>> commit the agreed to tickets to the 0.8.1 branch. If any tickets don't
>>> apply of course a back port patch has to happen through our standard
>>> process (not worried about that we have some engineering cycles to
>>> contribute to making that happen). Once that is all done, I will build
>>> 0.8.1.2 release artifacts and call a VOTE for RC1.
>>>
>>> /*******************************************
>>> Joe Stein
>>> Founder, Principal Consultant
>>> Big Data Open Source Security LLC
>>> http://www.stealth.ly
>>> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
>>> ********************************************/
>>>
>

Re: [DISCUSS] 0.8.1.2 Release

Posted by Jonathan Weeks <jo...@gmail.com>.
I was one asking for 0.8.1.2 a few weeks back, when 0.8.2 was at least 6-8 weeks out.

If we truly believe that 0.8.2 will go “golden” and stable in 2-3 weeks, I, for one, don’t need a 0.8.1.2, but it depends on the confidence in shipping 0.8.2 soonish.

YMMV,

-Jonathan


On Sep 30, 2014, at 12:37 PM, Neha Narkhede <ne...@gmail.com> wrote:

> Can we discuss the need for 0.8.1.2? I'm wondering if it's related to the
> timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in the
> next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just
> upgrade to 0.8.2?
> 
> On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly> wrote:
> 
>> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
>> 
>> Here are the JIRAs I would like to propose to back port a patch (if not
>> already done so) and apply them to the 0.8.1 branch for a 0.8.1.2 release
>> 
>> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
>> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for scala
>> 2.11)
>> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on
>> partition state update failures)
>> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew initial
>> setup output from source distribution)
>> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in our
>> src
>> release)
>> 
>> If the community and committers can comment on the patches proposed that
>> would be great. If I missed any bring them up or if you think any I have
>> proposed shouldn't be int he release bring that up too please.
>> 
>> Once we have consensus on this thread my thought was that I would apply and
>> commit the agreed to tickets to the 0.8.1 branch. If any tickets don't
>> apply of course a back port patch has to happen through our standard
>> process (not worried about that we have some engineering cycles to
>> contribute to making that happen). Once that is all done, I will build
>> 0.8.1.2 release artifacts and call a VOTE for RC1.
>> 
>> /*******************************************
>> Joe Stein
>> Founder, Principal Consultant
>> Big Data Open Source Security LLC
>> http://www.stealth.ly
>> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
>> ********************************************/
>> 


RE: [DISCUSS] 0.8.1.2 Release

Posted by "Seshadri, Balaji" <Ba...@dish.com>.
In DISH we are having issues in 0.8-beta version used in PROD, it's crashing every 2 days and becoming a blocker for us.

It would be great if we get 0.8.2 or 0.8.1.2 whichever is faster as we can't wait for 3 weeks as our new Order Management system is going to sit on top of Kafka.

-----Original Message-----
From: Neha Narkhede [mailto:neha.narkhede@gmail.com] 
Sent: Tuesday, September 30, 2014 1:37 PM
To: users@kafka.apache.org
Cc: dev@kafka.apache.org
Subject: Re: [DISCUSS] 0.8.1.2 Release

Can we discuss the need for 0.8.1.2? I'm wondering if it's related to the timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in the next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just upgrade to 0.8.2?

On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly> wrote:

> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
>
> Here are the JIRAs I would like to propose to back port a patch (if 
> not already done so) and apply them to the 0.8.1 branch for a 0.8.1.2 
> release
>
> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for 
> scala
> 2.11)
> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on 
> partition state update failures)
> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew 
> initial setup output from source distribution)
> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in 
> our src
> release)
>
> If the community and committers can comment on the patches proposed 
> that would be great. If I missed any bring them up or if you think any 
> I have proposed shouldn't be int he release bring that up too please.
>
> Once we have consensus on this thread my thought was that I would 
> apply and commit the agreed to tickets to the 0.8.1 branch. If any 
> tickets don't apply of course a back port patch has to happen through 
> our standard process (not worried about that we have some engineering 
> cycles to contribute to making that happen). Once that is all done, I 
> will build
> 0.8.1.2 release artifacts and call a VOTE for RC1.
>
> /*******************************************
>  Joe Stein
>  Founder, Principal Consultant
>  Big Data Open Source Security LLC
>  http://www.stealth.ly
>  Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> ********************************************/
>

Re: [DISCUSS] 0.8.1.2 Release

Posted by Jonathan Weeks <jo...@gmail.com>.
I was one asking for 0.8.1.2 a few weeks back, when 0.8.2 was at least 6-8 weeks out.

If we truly believe that 0.8.2 will go “golden” and stable in 2-3 weeks, I, for one, don’t need a 0.8.1.2, but it depends on the confidence in shipping 0.8.2 soonish.

YMMV,

-Jonathan


On Sep 30, 2014, at 12:37 PM, Neha Narkhede <ne...@gmail.com> wrote:

> Can we discuss the need for 0.8.1.2? I'm wondering if it's related to the
> timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in the
> next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just
> upgrade to 0.8.2?
> 
> On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly> wrote:
> 
>> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
>> 
>> Here are the JIRAs I would like to propose to back port a patch (if not
>> already done so) and apply them to the 0.8.1 branch for a 0.8.1.2 release
>> 
>> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
>> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for scala
>> 2.11)
>> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on
>> partition state update failures)
>> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew initial
>> setup output from source distribution)
>> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in our
>> src
>> release)
>> 
>> If the community and committers can comment on the patches proposed that
>> would be great. If I missed any bring them up or if you think any I have
>> proposed shouldn't be int he release bring that up too please.
>> 
>> Once we have consensus on this thread my thought was that I would apply and
>> commit the agreed to tickets to the 0.8.1 branch. If any tickets don't
>> apply of course a back port patch has to happen through our standard
>> process (not worried about that we have some engineering cycles to
>> contribute to making that happen). Once that is all done, I will build
>> 0.8.1.2 release artifacts and call a VOTE for RC1.
>> 
>> /*******************************************
>> Joe Stein
>> Founder, Principal Consultant
>> Big Data Open Source Security LLC
>> http://www.stealth.ly
>> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
>> ********************************************/
>> 


Re: [DISCUSS] 0.8.1.2 Release

Posted by Neha Narkhede <ne...@gmail.com>.
Can we discuss the need for 0.8.1.2? I'm wondering if it's related to the
timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in the
next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just
upgrade to 0.8.2?

On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly> wrote:

> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
>
> Here are the JIRAs I would like to propose to back port a patch (if not
> already done so) and apply them to the 0.8.1 branch for a 0.8.1.2 release
>
> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for scala
> 2.11)
> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on
> partition state update failures)
> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew initial
> setup output from source distribution)
> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in our
> src
> release)
>
> If the community and committers can comment on the patches proposed that
> would be great. If I missed any bring them up or if you think any I have
> proposed shouldn't be int he release bring that up too please.
>
> Once we have consensus on this thread my thought was that I would apply and
> commit the agreed to tickets to the 0.8.1 branch. If any tickets don't
> apply of course a back port patch has to happen through our standard
> process (not worried about that we have some engineering cycles to
> contribute to making that happen). Once that is all done, I will build
> 0.8.1.2 release artifacts and call a VOTE for RC1.
>
> /*******************************************
>  Joe Stein
>  Founder, Principal Consultant
>  Big Data Open Source Security LLC
>  http://www.stealth.ly
>  Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> ********************************************/
>

Re: [DISCUSS] 0.8.1.2 Release

Posted by Neha Narkhede <ne...@gmail.com>.
Can we discuss the need for 0.8.1.2? I'm wondering if it's related to the
timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in the
next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just
upgrade to 0.8.2?

On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <jo...@stealth.ly> wrote:

> Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release.
>
> Here are the JIRAs I would like to propose to back port a patch (if not
> already done so) and apply them to the 0.8.1 branch for a 0.8.1.2 release
>
> https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty)
> https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for scala
> 2.11)
> https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on
> partition state update failures)
> https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew initial
> setup output from source distribution)
> https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in our
> src
> release)
>
> If the community and committers can comment on the patches proposed that
> would be great. If I missed any bring them up or if you think any I have
> proposed shouldn't be int he release bring that up too please.
>
> Once we have consensus on this thread my thought was that I would apply and
> commit the agreed to tickets to the 0.8.1 branch. If any tickets don't
> apply of course a back port patch has to happen through our standard
> process (not worried about that we have some engineering cycles to
> contribute to making that happen). Once that is all done, I will build
> 0.8.1.2 release artifacts and call a VOTE for RC1.
>
> /*******************************************
>  Joe Stein
>  Founder, Principal Consultant
>  Big Data Open Source Security LLC
>  http://www.stealth.ly
>  Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> ********************************************/
>