Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: 98.139.253.105 is neither permitted
 nor denied by domain of evans@yahoo-inc.com)
From: Robert Evans <evans@yahoo-inc.com>
To: "general@hadoop.apache.org" <general@hadoop.apache.org>
Date: Tue, 28 Aug 2012 13:35:46 -0700
Subject: Re: svn branches cleanup
Thread-Topic: svn branches cleanup
Thread-Index: Ac2FXLV+XyT5kOIbQOa7KnZl//Wy7g==
Message-ID: <CC6295B4.7164%evans@yahoo-inc.com>
In-Reply-To: <41674E61-DF5C-425F-9B6E-C1415502660A@hortonworks.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I am fine with 23.1 and 23.2 going away, so long as 23.1 has a tag.

--Bobby

On 8/28/12 1:36 PM, "Vinod Kumar Vavilapalli" <vinodkv@hortonworks.com>
wrote:

>
>Thanks Bobby, makes sense to keep 0.23.3 as is for now.
>
>What about my comments about 23.1 and 23.2?
>
>Thanks,
>+Vinod
>
>On Aug 28, 2012, at 6:47 AM, Robert Evans wrote:
>
>> I plan to do a RC of 0.23.3 in the next few days.  I am waiting for some
>> tests of what is on branch-0.23 right now to pass before I create the
>> branch.  MAPREDUCE-3943 went in recently and it is big enough I want
>>some
>> more tests before I feel comfortable with it.  The tests for it so far
>> look good so I expect to get started on it today or tomorrow, but I have
>> never done a release before so I am sure it will take me a few days to
>>get
>> everything right. Also I don't see any reason to branch early when all
>> that is going in is bug fixes.
>>=20
>> --Bobby Evans
>>=20
>>=20
>> On 8/27/12 8:55 PM, "Vinod Kumar Vavilapalli" <vinodkv@hortonworks.com>
>> wrote:
>>=20
>>> Seems to me that stale branches have started accumulating. Here's what
>>>I
>>> am thinking.
>>>=20
>>> 2.* line
>>> - 2.0.1-alpha is released, so branch-2.0.1-alpha should instead be
>>> called branch-2.0.2-alpha?
>>>=20
>>> 0.23.* line
>>> - 0.23.1 was released long time back, so knock off branch-0.23.1
>>> altogether?
>>> - 0.23.2 seems to be dead, so knock off branch-0.23.2 too?
>>> - 0.23.3 is the next expected release, so I suppose all the commits are
>>> going into branch-0.23. Either we can
>>>   -- create branch-0.23.3 out of branch-0.23 now itself or
>>>   -- commit as is to branch-0.23 and create RC out of the same whenever
>>> that happens.
>>>=20
>>> Thanks,
>>> +Vinod
>>> PS: I missed action for ~1 month, please correct me if I am wrong.
>>=20
>