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 C25FB3A79 for ; Wed, 4 May 2011 04:08:20 +0000 (UTC) Received: (qmail 31416 invoked by uid 500); 4 May 2011 04:08:20 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 31303 invoked by uid 500); 4 May 2011 04:08:19 -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 31293 invoked by uid 99); 4 May 2011 04:08:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 May 2011 04:08:18 +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 (nike.apache.org: domain of saint.ack@gmail.com designates 209.85.216.176 as permitted sender) Received: from [209.85.216.176] (HELO mail-qy0-f176.google.com) (209.85.216.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 May 2011 04:08:10 +0000 Received: by qyk30 with SMTP id 30so676245qyk.14 for ; Tue, 03 May 2011 21:07:49 -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; bh=+r7r43E/XctQlzCt9wMbNJTXZ+20rtUzyw7zL++6Hfg=; b=ey7O6nZFthshpdlmMfVHxusa5ZSFlQszruHfq7A17CFsZgzMDpwzRX+tDb982qot2T I6SAKsCdPdg/oeTwiTPLlKMm/tKofzjiXNy92h9+akB2GIr4XkAZK+CWfu35vKFyDJod 76wrhKYpBO6uKG4dzyoalPM8hH6mehRw78Kbc= 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; b=X6F3VjUwahNXIyOTU2e3zjF2cqVewP1ELM4PIsE1TCEA/4+eXA0h2yYP2YQpVfFRgS eLby82iB7wL4hRA0lpdLy6Id+meEuCkhn1G2xMAooFSBKo1FKnVO8c/XOo6mEplsi7pE oKhN6M0G+tPVCLC8968fqsbQZfyfIteDfAQzY= MIME-Version: 1.0 Received: by 10.224.218.194 with SMTP id hr2mr645009qab.65.1304482069854; Tue, 03 May 2011 21:07:49 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.224.29.6 with HTTP; Tue, 3 May 2011 21:07:49 -0700 (PDT) In-Reply-To: References: Date: Tue, 3 May 2011 21:07:49 -0700 X-Google-Sender-Auth: 0kpFKQK36VuMSkDdy0jqgSVCzBM Message-ID: Subject: Re: Release 0.90.3 soon? From: Stack To: dev@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org IMO, HBASE-3777 is a critical fix -- it even addresses a regression introduced in 0.90.0 -- but its too risky putting it out now in a release from branch, at least just yet. It was only committed a day or so ago (Thanks Karthick and Ted for the hard work getting it in). I think it needs a bit of bake-in. We should be rolling a 0.92.0RC pretty soon. It'll get some testing then. We can not risk a point release that is less stable than previous versions; if we err, the cost in terms of support and community trust is just too high. Meantime, any chance of a backport of hbase-3777 Ted? Good stuff, St.Ack On Tue, May 3, 2011 at 6:00 PM, Ted Yu wrote: > The possibility of HBASE-3777 creating bigger trouble than without is low, > in my opinion. > Maybe we should conduct a poll in user mailing list and count the votes. > > On Tue, May 3, 2011 at 5:34 PM, Jean-Daniel Cryans wrote: > >> > Actually these two actions are related. >> > I can imagine the disappointment among hbase users if HBASE-3777 weren't >> > included in 0.90.3 >> >> I can also imagine the disappointment if we release a 0.90.3 that >> contains more bugs than it fixes, it goes both ways. Moreover, >> HBASE-3777 wasn't targeted and still isn't targeted for 0.90.3, so I >> don't see how even if someone paid attention to the jira they would >> expect to see it in 0.90.3 >> >> I'd like to state that I'm not trying to discredit the work that was >> done in that Jira, it was a perfect example of open source >> collaboration, but I'm rather trying to point out that it's a big >> change and that the bigger the change the better the chances are that >> there will be bugs lurking in it. You could easily list big patches >> that were committed to point releases in the past and I would agree >> with you that this is something we've done, but I can also recall a >> number of those changes that introduced more bugs and even made some >> releases unusable (like 0.20.4). Let's try to learn from our errors. >> >> Finally, even if it's not in 0.90.3, the fact that a backport be made >> available means that people can patch it in themselves or that other >> distros can decide to include it (like in the next CDH3 update). And >> finally we could do a 0.90.4 with it. >> >> J-D >> >