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

+1

Seems reasonable for the short term. Thanks for taking this over Robert!

On Apr 2, 2012, at 8:15 AM, Robert Evans 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
>

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

+1, this sounds like a good idea to me, Bobby.

On Mon, Apr 2, 2012 at 8:15 AM, Robert Evans <[EMAIL PROTECTED]> wrote:

> 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.
>

Note that HDFS HA and HDFS-PB are already on branch-0.23, as well as
branch-2.

--
Aaron T. Myers
Software Engineer, Cloudera

+1

Per ATM, you'll need to rename branch-0.23.2 to branch-0.23.0 to get
the code you want.

Thanks,
Eli

On Mon, Apr 2, 2012 at 8:15 AM, Robert Evans <[EMAIL PROTECTED]> 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
>

On Mon, Apr 2, 2012 at 10:53 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
> +1
>
> Per ATM, you'll need to rename branch-0.23.2 to branch-0.23.0 to get

Arg, that should have read branch-0.23 (no ".0").

+1 for leaving 0.23.2 as branch-0.23 for the short term, while branch-0.2 stabilizes in parallel.

Thanks,
+Vinod
On Apr 2, 2012, at 8:15 AM, Robert Evans 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
>

Eli,

Yes when Arun did all the renaming of branches for 2.0 branch-0.23.2 was renamed to branch-0.23 already.

--
Bobby

On 4/2/12 12:54 PM, "Eli Collins" <[EMAIL PROTECTED]> wrote:

On Mon, Apr 2, 2012 at 10:53 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
> +1
>
> Per ATM, you'll need to rename branch-0.23.2 to branch-0.23.0 to get

Arg, that should have read branch-0.23 (no ".0").

On Apr 2, 2012, at 10:49 AM, Aaron T. Myers wrote:
>
> Note that HDFS HA and HDFS-PB are already on branch-0.23, as well as
> branch-2.
>

Per the note I sent out to common-dev@ when I rolled hadoop-0.23.2-rc0, I've already copied branch-0.23.2 over to branch-0.23.

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

On Mon, Apr 2, 2012 at 11:03 AM, Robert Evans <[EMAIL PROTECTED]> wrote:

> Yes when Arun did all the renaming of branches for 2.0 branch-0.23.2 was
> renamed to branch-0.23 already.
>

Ah, my mistake. I must've missed the note. Seems like we're all good, then.
The branches are in the state that I would expect them to be.

Thanks a lot,
Aaron

--
Aaron T. Myers
Software Engineer, Cloudera

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 <[EMAIL PROTECTED]> 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
>

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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>

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.

Thanks,
Eli

On Wed, Apr 18, 2012 at 1:39 PM, Robert Evans <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>
>