Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of atm@cloudera.com designates
 209.85.212.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <94AFEFD4-DEC8-4750-A1C6-CE4268E333B4@hortonworks.com>
References: <C2180ED3-51B8-407C-96BA-6A59E37E39B4@hortonworks.com>
 <8EB84C43-6949-4715-A77D-1B6F5EC3913A@hortonworks.com>
 <94AFEFD4-DEC8-4750-A1C6-CE4268E333B4@hortonworks.com>
From: "Aaron T. Myers" <atm@cloudera.com>
Date: Wed, 28 Mar 2012 00:48:31 -0700
Message-ID: 
 <CA+4052nMGB-b+dqMs=vFRw0X1z8s34WzFaZN-P3aP5YFxePUBA@mail.gmail.com>
Subject: Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x
To: hdfs-dev@hadoop.apache.org
Cc: common-dev@hadoop.apache.org, mapreduce-dev@hadoop.apache.org
Content-Type: multipart/alternative; boundary=20cf307f353e3b498f04bc48d7c3

--20cf307f353e3b498f04bc48d7c3
Content-Type: text/plain; charset=ISO-8859-1

Hey Arun,

On Wed, Mar 28, 2012 at 12:28 AM, Arun C Murthy <acm@hortonworks.com> wrote:

> Done, all clear; I've also created jira revisions. Please let me know if
> you find any issues.
>

Thanks a lot for making these changes. Two questions:

- Now that we've renamed branch-0.23 to branch-2, and since there is as yet
no branch-0.23.3, what should be done with JIRAs marked with the 0.23.3
version? Perhaps all of these should be updated to 2.0.0?

- We still have the JIRA version 0.24.0, which is presumably still
representative of trunk. Given that we will likely never release an 0.24.0,
should we rename this version in JIRA as well?

--
Aaron T. Myers
Software Engineer, Cloudera

--20cf307f353e3b498f04bc48d7c3--