Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-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 71A96743C for ; Wed, 3 Aug 2011 17:28:22 +0000 (UTC) Received: (qmail 17510 invoked by uid 500); 3 Aug 2011 17:28:21 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 17288 invoked by uid 500); 3 Aug 2011 17:28:20 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 17280 invoked by uid 99); 3 Aug 2011 17:28:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Aug 2011 17:28:20 +0000 X-ASF-Spam-Status: No, hits=-1.6 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [192.6.10.60] (HELO tobor.hpl.hp.com) (192.6.10.60) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Aug 2011 17:28:13 +0000 Received: from localhost (localhost [127.0.0.1]) by tobor.hpl.hp.com (Postfix) with ESMTP id 8B137B7F45 for ; Wed, 3 Aug 2011 18:27:51 +0100 (BST) X-Virus-Scanned: amavisd-new at hplb.hpl.hp.com Received: from tobor.hpl.hp.com ([127.0.0.1]) by localhost (tobor.hpl.hp.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id B2lIVofXRmcw for ; Wed, 3 Aug 2011 18:27:40 +0100 (BST) Received: by tobor.hpl.hp.com (Postfix, from userid 1001) id 78DA3B7FA3; Wed, 3 Aug 2011 16:28:39 +0100 (BST) Received: by tobor.hpl.hp.com (Postfix, from userid 1001) id 0BC5EB7FA5; Wed, 3 Aug 2011 17:18:43 +0100 (BST) Received: from 0-imap-br1.hpl.hp.com (0-imap-br1.hpl.hp.com [16.25.144.60]) by tobor.hpl.hp.com (Postfix) with ESMTP id 952D8B8996 for ; Wed, 3 Aug 2011 14:57:25 +0100 (BST) MailScanner-NULL-Check: 1312984630.25617@1yXoNwXQjsDE3n9MDk/C5g Received: from [16.25.175.86] (wildhaus.hpl.hp.com [16.25.175.86]) by 0-imap-br1.hpl.hp.com (8.14.1/8.13.4) with ESMTP id p73Dv9iZ013627 for ; Wed, 3 Aug 2011 14:57:09 +0100 (BST) Message-ID: <4E3953B0.208@apache.org> Date: Wed, 03 Aug 2011 14:57:04 +0100 From: Steve Loughran User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11 MIME-Version: 1.0 To: common-dev@hadoop.apache.org Subject: Re: [VOTE] Release 0.20.204.0-rc0 References: <6C8A17F4-97AB-497B-83CC-BB853E842C0E@hortonworks.com> <645195E6D08FFB4B9D81BB747CDF051B5A0F80@CORPUSMX10A.corp.emc.com> <576E7EB3-3278-4A53-9482-CB8B3DAD6683@hortonworks.com> <4E3293BC.6040608@apache.org> <4E37DF66.2050109@apache.org> <10525873-1AA9-40D7-8F75-A3B3BC306004@apache.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HPL-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: p73Dv9iZ013627 X-HPL-MailScanner: Found to be clean X-HPL-MailScanner-From: stevel@apache.org On 02/08/11 20:23, Eli Collins wrote: > On Tue, Aug 2, 2011 at 11:08 AM, Allen Wittenauer wrote: >> >> On Aug 2, 2011, at 4:28 AM, Steve Loughran wrote: >>> >>> I'm getting confused about release roadmaps right now >> >> branch-20 is the new trunk, given that features keep popping up in it rather than bug fixes. > > When we voted to adopt 203.rc0 we also voted to adopt the new 4 part > version scheme which was intended to allow feature development on the > 203.x series. See http://search-hadoop.com/m/iegPf7aDvh1 This makes things clearer. Now, if I were to propagate a change from trunk to the 0.20.20x branch by committing it to https://svn.apache.org/repos/asf/hadoop/common/branches/branch-0.20-security-204/ , that's going to get into .204? Yet my proposal to do what was rejected, saying "hold for .205". Should someone create a .205 branch so that we can backport all non-critical patches for the 20.20x line into there, while the 0.20.204 becomes frozen for the release except for absolutely critical patches?