Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-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 95A5D6C59 for ; Mon, 16 May 2011 18:31:29 +0000 (UTC) Received: (qmail 87055 invoked by uid 500); 16 May 2011 18:31:29 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 87023 invoked by uid 500); 16 May 2011 18:31:29 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 87015 invoked by uid 99); 16 May 2011 18:31:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2011 18:31:29 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 209.85.213.169 as permitted sender) Received: from [209.85.213.169] (HELO mail-yx0-f169.google.com) (209.85.213.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2011 18:31:24 +0000 Received: by yxt33 with SMTP id 33so2202532yxt.14 for ; Mon, 16 May 2011 11:31:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=PKnno86JX5BnqQQ2POp+CKfcpv4SQhhJLBjG5Xkvp2U=; b=iV8vfVI6J0PMgOnTQeA9fX371DqhssSWh0Boka0adiSXcQ64VQS6sLNzdRfv73G7xL 6463vLFSoeH+lIa6KmvBUV8XSFtxT8JJM0fIcxMJbKff/cbTdA/X0oDKFx/g2T9YIYmT 8jW4fP6rlQ+E+qFt2dOrAVpfBHKmd8eqnZFhs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=wmxw0RJYwFPTym0yJPomfeTc8tVMPvHkZz1ZqCZMTnI1yKgPtzPecrPrWyWgFgNdXD Y4Cbas06QO0iSYaoDHMn4eLeP8v6emcQXt9srSun7P5HnAngV2MTlG3hBj3PFVdzSGZW py0JlpQQ4fr4LwXxcJXmT94EcD2wMv0aeBM34= MIME-Version: 1.0 Received: by 10.101.27.40 with SMTP id e40mr2600589anj.0.1305570663590; Mon, 16 May 2011 11:31:03 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.100.8.4 with HTTP; Mon, 16 May 2011 11:31:03 -0700 (PDT) In-Reply-To: References: Date: Mon, 16 May 2011 11:31:03 -0700 X-Google-Sender-Auth: 3EQkUOjRre004CZprHo5v1hCXsE Message-ID: Subject: Re: Release 0.90.3 soon? From: Jean-Daniel Cryans To: dev@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Run the unit tests, try it on a handful of machines, basically just make sure it's usable. J-D On Mon, May 16, 2011 at 11:26 AM, Ted Yu wrote: > I assume release manager has to be a committer. So, although I want to he= lp > ... > > On Mon, May 16, 2011 at 11:00 AM, Stack wrote: > >> We cut cut a 0.91 now as Todd suggests but would need a release >> manager to run the release. >> St.Ack >> >> On Mon, May 16, 2011 at 9:26 AM, Ted Yu wrote: >> > Barney Frank's request for help brought me back to this discussion. >> > When would 0.91 release come ? >> > >> > On Wed, May 4, 2011 at 10:31 AM, Ted Yu wrote: >> > >> >> I am looking forward to this 0.91 release. >> >> >> >> >> >> On Wed, May 4, 2011 at 10:23 AM, Todd Lipcon wrot= e: >> >> >> >>> On Wed, May 4, 2011 at 8:57 AM, Ted Yu wrote: >> >>> >> >>> > When would 0.91 branch be created ? >> >>> > We should reduce the number of open critical bugs for 0.90 - each >> such >> >>> > issue >> >>> > would soon be integrated to 3 branches after 0.91 branch is create= d. >> >>> > >> >>> >> >>> Sorry, I should have been clear that I would imagine 0.91 would be a >> "dev >> >>> release" series like 0.89. That is to say, there would be no 0.91 >> branch, >> >>> just a few "snapshot style" releases with minimal pre-release testin= g >> to >> >>> get >> >>> us in shape for 92. These releases would never have point releases d= one >> on >> >>> top (and thus not need to have changes backported to them one >> released). >> >>> >> >>> Consider it another name for an extended release candidate period fo= r >> >>> 0.92. >> >>> >> >>> -Todd >> >>> >> >>> >> >>> > On Tue, May 3, 2011 at 10:47 PM, Todd Lipcon >> wrote: >> >>> > >> >>> > > Maybe we should do an 0.91 dev release tout de suite? Folks who >> want >> >>> > > 3777 and coprocessors and the other nice stuff can then help us >> bake >> >>> > > towards 92 ? >> >>> > > >> >>> > > Todd >> >>> > > >> >>> > > On Tuesday, May 3, 2011, Stack wrote: >> >>> > > > On Tue, May 3, 2011 at 9:21 PM, Ted Yu >> wrote: >> >>> > > >> After discussion below, I wonder if 0.92.0RC would come out >> before >> >>> > > 0.90.4 >> >>> > > >> I hope that's the case - we're looking forward to coprocessor >> which >> >>> > > wouldn't >> >>> > > >> be in 0.90.x anyway. >> >>> > > >> >> >>> > > > >> >>> > > > Plan is to put up a 0.92.0 'soon', in the next week or so. =A0= I'm >> not >> >>> > > > sure when 0.90.4 will see light of day. =A0There's a good few >> blockers >> >>> > > > and criticals but if a few of us have a go at them, we'll knoc= k >> it >> >>> out >> >>> > > > tout de suite (This is what I'm working on at mo). >> >>> > > > >> >>> > > > Good stuff, >> >>> > > > St.Ack >> >>> > > > >> >>> > > >> >>> > > -- >> >>> > > Todd Lipcon >> >>> > > Software Engineer, Cloudera >> >>> > > >> >>> > >> >>> >> >>> >> >>> >> >>> -- >> >>> Todd Lipcon >> >>> Software Engineer, Cloudera >> >>> >> >> >> >> >> > >> >