Return-Path: 
 <dev-return-22102-apmail-kafka-dev-archive=kafka.apache.org@kafka.apache.org>
X-Original-To: apmail-kafka-dev-archive@www.apache.org
Delivered-To: apmail-kafka-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id DB02E1760C
	for <apmail-kafka-dev-archive@www.apache.org>;
 Thu,  2 Oct 2014 21:48:25 +0000 (UTC)
Received: (qmail 94917 invoked by uid 500); 2 Oct 2014 21:48:25 -0000
Delivered-To: apmail-kafka-dev-archive@kafka.apache.org
Received: (qmail 94866 invoked by uid 500); 2 Oct 2014 21:48:25 -0000
Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@kafka.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@kafka.apache.org>
List-Post: <mailto:dev@kafka.apache.org>
List-Id: <dev.kafka.apache.org>
Reply-To: dev@kafka.apache.org
Delivered-To: mailing list dev@kafka.apache.org
Received: (qmail 94843 invoked by uid 99); 2 Oct 2014 21:48:24 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Oct 2014 21:48:24 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of junrao@gmail.com designates
 209.85.214.173 as permitted sender)
Received: from [209.85.214.173] (HELO mail-ob0-f173.google.com)
 (209.85.214.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Oct 2014 21:47:58 +0000
Received: by mail-ob0-f173.google.com with SMTP id wp4so13768obc.18
        for <multiple recipients>; Thu, 02 Oct 2014 14:47:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=bisxiqCohJHT2Fte8hQ3d+8fXB/yO8iEEAIVuwgTKiU=;
        b=Rf34vEau2JYpKPZQ0LD3n+8tuj5g0oRe5ZvWFhWXiEutx9PtQcwbHwTrdvK84qx6Iw
         8fiY4rtkma/dxeImIBXqZHj1FJL24aQ3G2eRMn99l69yPAGnAii5BnqVV5NBMa02+ugZ
         GPRIVxFw1yeq62QPt7HxyixX1FdVQncTqBKNbQIYs+c9NaaTz8Ly1YNHFfTrVybsbAql
         HOb6ENPqw2fqICIIXqgWvAbzWvz++4VG7payCNVRE5GpFLUcq2l9wT4u86oNsrPTYTXD
         haCrPQpHdQVs3yk3LcPEO29IqTWMCmGiHFiIcRVE1GkDzCin+D40lZ/8wZsumFMEcvno
         DB2A==
MIME-Version: 1.0
X-Received: by 10.182.142.67 with SMTP id ru3mr1952062obb.15.1412286477034;
 Thu, 02 Oct 2014 14:47:57 -0700 (PDT)
Received: by 10.60.96.9 with HTTP; Thu, 2 Oct 2014 14:47:56 -0700 (PDT)
In-Reply-To: 
 <CAJARbTRsdei9uUoiw2Vvd3Bxo5EhqPUpwGze=_6M9f9f2DnPqg@mail.gmail.com>
References: 
 <CAA7ooCD9LxgXZnXHhp1wA+WUfrog6x8pkZ9JnWkJt7DCYorUhg@mail.gmail.com>
	<CAOG_4QaS3G_EsX=VD2xyPXYhKdwxZ4KdFzDR-Mx9TjqkRHeYuQ@mail.gmail.com>
	<71DB56D9-6BD9-4A7F-AAC1-29A5F88BE4EC@gmail.com>
	<CAJARbTRsdei9uUoiw2Vvd3Bxo5EhqPUpwGze=_6M9f9f2DnPqg@mail.gmail.com>
Date: Thu, 2 Oct 2014 14:47:56 -0700
Message-ID: 
 <CAFbh0Q1vHQeKYNRWU1zmJtzJZj3rpKBcX29YtUyeaEgMC141TQ@mail.gmail.com>
Subject: Re: [DISCUSS] 0.8.1.2 Release
From: Jun Rao <junrao@gmail.com>
To: "users@kafka.apache.org" <users@kafka.apache.org>
Cc: "dev@kafka.apache.org" <dev@kafka.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2eceac8ebd1050477918a
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c2eceac8ebd1050477918a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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=3D-4&jql=3Dproject%=
20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reo=
pened%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 <kane.isturm@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
> <jonathanbweeks@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 =E2=80=9Cgolden=E2=80=9D and sta=
ble in 2-3 weeks,
> I, for one, don=E2=80=99t need a 0.8.1.2, but it depends on the confidenc=
e in
> shipping 0.8.2 soonish.
> >
> > YMMV,
> >
> > -Jonathan
> >
> >
> > On Sep 30, 2014, at 12:37 PM, Neha Narkhede <neha.narkhede@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 <joe.stein@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 n=
ot
> >>> 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 buil=
d
> >>> 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>
> >>> ********************************************/
> >>>
> >
>

--001a11c2eceac8ebd1050477918a--