Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 4122 invoked from network); 7 Apr 2010 18:48:12 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Apr 2010 18:48:12 -0000 Received: (qmail 83880 invoked by uid 500); 7 Apr 2010 18:41:31 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 83859 invoked by uid 500); 7 Apr 2010 18:41:31 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 83851 invoked by uid 99); 7 Apr 2010 18:41:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Apr 2010 18:41:31 +0000 X-ASF-Spam-Status: No, hits=-0.9 required=10.0 tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,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.211.174 as permitted sender) Received: from [209.85.211.174] (HELO mail-yw0-f174.google.com) (209.85.211.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Apr 2010 18:41:24 +0000 Received: by ywh4 with SMTP id 4so658730ywh.5 for ; Wed, 07 Apr 2010 11:41:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:received:message-id:subject :from:to:content-type; bh=oUM3kDhmybPAWW7/KGuF9kCkMxl6aC8QRmaXxEykWl4=; b=nZM8EoKKleAhSk7ow7PlUPH9h0+wHJaac5t1lyQO4THxtq3oHtvtd7uMNGP060AcCU KxkLlGuJeC/EXykqNao+PQ5VoT1o2MZ95JhBHdhfDm9kktLysD/c4pgOth3HZXjukPEG gza+l2vb28qY28TND9G8rMd0EpCH0lrE8MJtQ= 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=fsmPpaGMb423kJJ8opPN8BEXUM3dbSL9uRzP93p5ZOYxEdrQFh27jQi/sKp5WbR5h3 D0+Rjr2iHC7XEwOTIlgYKLlWnaW6aolHqSyt8JV42dJvMuUaWYEhRhzeZhv3ObCXzo8j 4B3Vn4P2xtqwFlU3l5iWK2N9IRkd4jgvHQXrg= MIME-Version: 1.0 Sender: jdcryans@gmail.com Received: by 10.90.89.20 with HTTP; Wed, 7 Apr 2010 11:41:03 -0700 (PDT) In-Reply-To: References: <189815.52145.qm@web65513.mail.ac4.yahoo.com> Date: Wed, 7 Apr 2010 11:41:03 -0700 X-Google-Sender-Auth: 565effa6a917f1cd Received: by 10.91.59.6 with SMTP id m6mr888482agk.4.1270665664012; Wed, 07 Apr 2010 11:41:04 -0700 (PDT) Message-ID: Subject: Re: Vote on 0.20.3.1 From: Jean-Daniel Cryans To: hbase-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 > > I agree with Ryan that branching the release branch can get pretty > confusing. I've only seen a version number like 0.20.3.1 once before, and > that was for a completely botched release, where the .1 was a very very > minor fix on top of the first release. In this case, even though there > aren't any giant changes slated, there are changes that are large enough > that it seems dishonest to call it a "doubly minor" release on top of > 0.20.3. We already agreed to call it 0.20.4 instead of 0.20.3.1 > > Regarding the bigger changes we have slated for 0.20 branch (eg durability > fixes, 2248), why not just call it 0.21 at that point? We've already decided > that future versions of HBase will be compatible with multiple versions of > Hadoop, so we can add these major changes for 0.21 and then make 0.22 the > next major release with replication, mvn, etc? This is for another discussion, I'd like to end this one first. > > -Todd >