hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eli Collins <...@cloudera.com>
Subject Re: [DISCUSS] branch-0.23 is dead, long live branch-0.23
Date Wed, 18 Apr 2012 20:58:20 GMT
Thanks Bobby. Your first pass looks good to me.
At least now all the 23.x jiras are either slated for 23.3 or 2.0.


On Wed, Apr 18, 2012 at 1:39 PM, Robert Evans <evans@yahoo-inc.com> wrote:
> Thanks Eli for catching that.  I have done a first pass at updating the tickets.  Please
check your jiras to be sure I did not make a mistake on any of them.  I will probably review
them in more depth soon.
> --Bobby
> On 4/18/12 2:13 PM, "Eli Collins" <eli@cloudera.com> wrote:
> Hey Bobby,
> These are the jiras (http://bit.ly/J4NYv0) marked with target version
> 0.23.3, if there are ones here that you don't plan to include in a
> 0.23.3 release mind If I give them to the 2.x target version instead?
> I noticed there are still a bunch of jiras with target version 0.23.1
> and 0.23.2 (even those have already been released / voted on), how
> about we give the jiras that you want from this list
> (http://bit.ly/HToh2Q) a 0.23.3 target version and we'll move the rest
> to 2.x?
> Thanks,
> Eli
> On Mon, Apr 2, 2012 at 8:15 AM, Robert Evans <evans@yahoo-inc.com> wrote:
>> At Yahoo we have been running hadoop-0.23.2 in an effort to stabilize it and
>> validate it with our internal customers.  I propose that we don't completely
>> kill off branch-0.23 just yet so that we can finish up this effort and make
>> some small sustaining releases (e.g. 0.23.3).  At the same time we are
>> starting to use hadoop-2 (with HDFS HA, HDFS-PB ...) as a second train.
>> As such, I volunteer to take over release management of branch-0.23.  Of
>> course I will treat branch 0.23 as a stabilizing line off of 2.0 and not
>> accept anything in that is not first in branch-2 and trunk.   Essentially,
>> this is something that we have to do either internally or publicly, and I
>> would much rather do this publicly.
>>  --Bobby Evans

View raw message