Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: Arun C Murthy <acm@hortonworks.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-76-333598552
Subject: Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x
Date: Wed, 28 Mar 2012 16:00:00 -0700
In-Reply-To: 
 <CA+4052nhtYA2RiD11aBHbi7EM52wVif6hfrv+JWErNj4xiCcvA@mail.gmail.com>
To: hdfs-dev@hadoop.apache.org,
 mapreduce-dev@hadoop.apache.org,
 common-dev@hadoop.apache.org
References: <C2180ED3-51B8-407C-96BA-6A59E37E39B4@hortonworks.com>
 <8EB84C43-6949-4715-A77D-1B6F5EC3913A@hortonworks.com>
 <94AFEFD4-DEC8-4750-A1C6-CE4268E333B4@hortonworks.com>
 <CA+4052nMGB-b+dqMs=vFRw0X1z8s34WzFaZN-P3aP5YFxePUBA@mail.gmail.com>
 <4CA90D06-4BBE-499E-98ED-F8A2B9236793@hortonworks.com>
 <CADY20s4mLKa5xrcgmQPA-DOyUptQ=Fch85cE2VGfTNePqSk61A@mail.gmail.com>
 <CA+4052mzKsqXhFVLChGKUVH=Fn3qLccz9-0nJMGw4KDRM4UpqQ@mail.gmail.com>
 <CADY20s7ZXOkZge8ecTO-h1K7z1jDKeBjuDTeGF9M8z4VMDvRfQ@mail.gmail.com>
 <CAHfHakHndB=ruQ-e3cELJgZg0MvoD5-_u1QfZWrmPO1y==ZjBw@mail.gmail.com>
 <CADY20s63qhGMTitz7DdPmoJL81+_i1G7ZZPrbmC1Hs6hMcOq1w@mail.gmail.com>
 <7294BB22-73B1-4D5D-97C2-D52CDD20E54B@hortonworks.com>
 <CA+4052nhtYA2RiD11aBHbi7EM52wVif6hfrv+JWErNj4xiCcvA@mail.gmail.com>
Message-Id: <7EAAB2F7-4FCF-4C1B-8334-F0EB4B1CC28C@hortonworks.com>

--Apple-Mail-76-333598552
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Mar 28, 2012, at 2:14 PM, Aaron T. Myers wrote:

> On Wed, Mar 28, 2012 at 1:57 PM, Arun C Murthy <acm@hortonworks.com> =
wrote:
>=20
>> On on hand, we've historically bumped the version number for trunk =
(i.e.
>> 3.0.0-SNAPSHOT). This has the nice property that when we do cut a =
release
>> branch off trunk we don't have to scramble to change fix-versions on =
all
>> the jiras committed to trunk from 'trunk' to X.0.0. Since I've done =
my fair
>> share of jira manipulation for releases as the RM, as recently as =
last
>> night, it's nice to not force the burden on the RM for branch-3.
>>=20
>=20
> I don't think you'd have to change all the JIRAs. You'd just have to =
change
> the name of the "trunk" JIRA version to whatever the right number is, =
and
> then create a new version in JIRA also named "trunk." This would serve =
the
> same purpose, without having to update any individual JIRAs.


Ah, I didn't know that, thanks for the tip. That alleviates my concerns.

Arun

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/


--Apple-Mail-76-333598552--