hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eli Collins <...@cloudera.com>
Subject Re: svn branches cleanup
Date Fri, 31 Aug 2012 21:54:48 GMT
On Fri, Aug 31, 2012 at 2:26 PM, Owen O'Malley <omalley@apache.org> wrote:
> On Mon, Aug 27, 2012 at 6:55 PM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
>
>> Seems to me that stale branches have started accumulating.
>
>
> I just cleaned up some obvious trash from the branches directory:
>
> MR-279
> MR-279-merge
> MR-279-merge-to-trunk
> yahoo-merge
>
> I'd also like to delete the now defunct and unreleased:
> branch-0.20-append
> branch-0.20-security-202
> branch-0.21-old
>
> I would like to rename the following release branches:
>
> branch-0.20-security-203 -> branch-0.20.203
> branch-0.20-security-204 -> branch-0.20.204
> branch-0.20-security-205 -> branch-0.20.205
>
> I believe the following ones should also be deleted:
> branch-0.23-PB
> branch-1.0.2 (equal to the tag/release-1.0.2)
>
>
>> Here's what I am thinking.
>>
>> 2.* line
>>  - 2.0.1-alpha is released, so branch-2.0.1-alpha should instead be called
>> branch-2.0.2-alpha?
>>
>
> We should rename the 2.x branches as:
> branch-2.0.1-alpha -> branch-2.0
> branch-2.1.0-alpha -> branch-2.1
>
>
>> 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.
>>
>
> There should only be a single 0.23 branch, so we should delete
> branch-0.23.0
> branch-0.23.1
> branch-0.23.2
>
> Any concerns?

Looks good to me.

I could go either way on the branch-2.x ones.

Mime
View raw message