Return-Path: X-Original-To: apmail-incubator-kafka-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-kafka-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5D2F1C4AE for ; Fri, 8 Jun 2012 18:31:13 +0000 (UTC) Received: (qmail 70290 invoked by uid 500); 8 Jun 2012 18:31:13 -0000 Delivered-To: apmail-incubator-kafka-dev-archive@incubator.apache.org Received: (qmail 70266 invoked by uid 500); 8 Jun 2012 18:31:13 -0000 Mailing-List: contact kafka-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: kafka-dev@incubator.apache.org Delivered-To: mailing list kafka-dev@incubator.apache.org Received: (qmail 70258 invoked by uid 99); 8 Jun 2012 18:31:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jun 2012 18:31:13 +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 (athena.apache.org: domain of jay.kreps@gmail.com designates 209.85.160.175 as permitted sender) Received: from [209.85.160.175] (HELO mail-gh0-f175.google.com) (209.85.160.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jun 2012 18:31:06 +0000 Received: by ghbz2 with SMTP id z2so1414469ghb.6 for ; Fri, 08 Jun 2012 11:30:46 -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 :content-type; bh=QExQyKMCR5D6YF6qsvWbXZSmOjndQSbQuFQapnTfUJ4=; b=t+CCeKvAO+U5NIEW4bTD6RtVJwC7QRbWO1y845mPV5URl286Ai7n0nv/JJeVtWv1kU InKTE5nVt+XwWnSoXsnhYyqg7cZkCV1ctdivyVxuHmJ8fS7HJ6Mq0kz62FwmsspLCCVN P9fB+IErBYx05U/rUiqzN5TxfD21qXfqO8I83TH5JBuHNbIWV62zhkJg6YUEIhbL/4yU R1NlK0kqV/LoTLoLo/n44G6fsu4yMWuiDh8i7hBuCKWLUfy8tKoZdKCIj7uTsGn5YAA2 8hemysER4K/U1RzvImns/+eaT+KGAWc3wd/JiWTaHkKRZTaz6tO3IWlzoVDGTK+nUg/7 V9Tg== MIME-Version: 1.0 Received: by 10.50.173.102 with SMTP id bj6mr3153221igc.25.1339180245937; Fri, 08 Jun 2012 11:30:45 -0700 (PDT) Received: by 10.231.22.27 with HTTP; Fri, 8 Jun 2012 11:30:45 -0700 (PDT) In-Reply-To: <56B918BC-D504-481D-A749-6BC8847249FC@gmail.com> References: <4FCEBDA2.3000505@gmail.com> <56B918BC-D504-481D-A749-6BC8847249FC@gmail.com> Date: Fri, 8 Jun 2012 11:30:45 -0700 Message-ID: Subject: Re: [DISCUSS] Graduate from incubator? From: Jay Kreps To: kafka-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=e89a8f83a6afd96cfa04c1fa32fd X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f83a6afd96cfa04c1fa32fd Content-Type: text/plain; charset=ISO-8859-1 That's awesome, Joe. So it sounds like the plan is to do a 0.7.1 release and then pursue graduation? There were a few who just wanted to go for it, any objection to waiting a bit to get this release out? -Jay On Fri, Jun 8, 2012 at 10:59 AM, Joe Stein wrote: > I would be interested to drive a 0.7.1 release. > > On Jun 8, 2012, at 12:23 PM, Jun Rao wrote: > > > Actually, any committers outside of LinkedIn is interested in drive an > > 0.7.1 release? That will help diversifying the community. It should be > much > > easier than the 0.7.0 release since most of the licensing issues have > been > > resolved. > > > > Thanks, > > > > Jun > > > > On Wed, Jun 6, 2012 at 5:46 PM, Joel Koshy wrote: > > > >> I think an 0.7.1 release would be suitable in any case given that there > are > >> few additional features and API changes since 0.7.0 - I can drive that, > >> although an 0.7.1 release need not necessarily hold up pursuing > graduation > >> if people prefer (1). > >> > >> Joel > >> > >> On Wed, Jun 6, 2012 at 12:51 PM, Jay Kreps wrote: > >> > >>> This is a fair point. I am not sure of the best practices on the number > >> of > >>> releases to do before graduation. The Incubator docs imply a fairly low > >>> bar: > >>> "Projects need to cut releases. Apache projects need to understand how > to > >>> cut Apache releases. Therefore it is an important step during your stay > >> in > >>> the incubator to demonstrate the ability to create an Apache Release. > >>> Podlings > >>> do not need to actually *publish* a release to demonstrate that they > >>> understand how to accomplish such a feat. However, creating a release > >> that > >>> is approved by the incubator project management > >>> committee< > >>> > >> > http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29 > >>>> > >>> is usually the simplest way to do this." > >>> (http://incubator.apache.org/guides/graduation.html#releases) > >>> > >>> They refer to "a release" not "releases", and mention that they don't > >>> particularly care if you publish it or not. We might want to set a > higher > >>> bar for ourselves, though. > >>> > >>> We had planned on having 0.8 be the next release, and that is still a > few > >>> months out I suspect. However we did take a number of minor features > and > >>> fixes post 0.7 that are only on trunk it would probably be possible to > >> do a > >>> 0.7.1 without too much drama and that would make that work available to > >>> people in a more easily consumable form . On the other hand it would be > >>> nice to just be heads down and focus on 0.8 too. So if people agree > with > >>> Chris's feedback there are three options: > >>> > >>> 1. Pursue graduation now > >>> 2. Do a 0.7.1 release, pursue graduation when that is completed > >>> 3. Wait until 0.8 is out, pursue graduation after that > >>> > >>> Anyone have a strong preference for one of these options? > >>> > >>> -Jay > >>> > >>> On Tue, Jun 5, 2012 at 7:17 PM, Chris Burroughs > >>> wrote: > >>> > >>>> On 2012-05-23 23:32, Alan D. Cabrera wrote: > >>>>>> We struggled a bit with licensing and packaging issues but we got > >>> those > >>>>>> issues resolved and did a release and this should be pretty easy > >> going > >>>>>> forward. > >>>> > >>>> This is the one point I am hesitant about. I think it would be > >>>> reasonable to ask us for a history of more than a single release (and > >>>> I'm not sure we got the mirror situation 100% right yet). We sure we > >>>> got this one? > >>>> > >>>> For the more important parts, It's exciting to see the community grow > >>>> (particular the diversity part, that's a great accomplishment and I > >> know > >>>> takes significant commitment). On that note I would be interested in > >>>> hearing from other committers about graduation. > >>>> > >>> > >> > --e89a8f83a6afd96cfa04c1fa32fd--