Hi All,

 It's looking like trunk is moving along rapidly - it's about time to start thinking of the next release to unlock all of the goodies there.

 As the RM, my current thinking is that after we merge NextGen MR (MR-279) and the HDFS-1073 branch into trunk we should be good to create the hadoop-0.23 branch.

 Thoughts?

thanks,
Arun

Good morning!

On Jul 13, 2011, at 3:39 PM, Arun C Murthy wrote:

> It's looking like trunk is moving along rapidly - it's about time to start thinking of the next release to unlock all of the goodies there.
>
> As the RM, my current thinking is that after we merge NextGen MR (MR-279) and the HDFS-1073 branch into trunk we should be good to create the hadoop-0.23 branch.

Since the last time we spoke (actually, since last night, in fact!) the world (trunk) has changed to accommodate our wishes... *smile*

HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's time to cut the 0.23 branch so that we can focus on testing and stabilizing a hadoop-0.23 release off that branch.

I propose to do it noon of the coming Monday (Aug 22).

Thoughts?

thanks,
Arun

On Thu, Aug 18, 2011 at 9:36 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
> Good morning!
>
> On Jul 13, 2011, at 3:39 PM, Arun C Murthy wrote:
>
>> It's looking like trunk is moving along rapidly - it's about time to start thinking of the next release to unlock all of the goodies there.
>>
>> As the RM, my current thinking is that after we merge NextGen MR (MR-279) and the HDFS-1073 branch into trunk we should be good to create the hadoop-0.23 branch.
>
> Since the last time we spoke (actually, since last night, in fact!) the world (trunk) has changed to accommodate our wishes... *smile*
>
> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's time to cut the 0.23 branch so that we can focus on testing and stabilizing a hadoop-0.23 release off that branch.
>
> I propose to do it noon of the coming Monday (Aug 22).
>
> Thoughts?

I assume we will make sure the HDFS mavenization is in before then?
Tom said he intends to commit it tomorrow, but if something comes up
and it's not committed, let's make sure mavenization happens before we
branch.

Also, what will be the guidelines for committing a change to 0.23
branch? Is it "bug fix only" or are we still allowing improvements?
Given how recently MR2 was merged, I imagine there will be a lot of
things that aren't strictly bugs that we will really want to have in
our next release. I also have a couple of HDFS patches (eg the new
faster CRC on-by-default) that I'd like to get into 23.

-Todd
--
Todd Lipcon
Software Engineer, Cloudera

On Aug 18, 2011, at 1:21 PM, Todd Lipcon wrote:
>>
>> I propose to do it noon of the coming Monday (Aug 22).
>>
>> Thoughts?
>
> I assume we will make sure the HDFS mavenization is in before then?
> Tom said he intends to commit it tomorrow, but if something comes up
> and it's not committed, let's make sure mavenization happens before we
> branch.

Yes, I assume it will be done too. I see a flurry of activity from Alejandro, Tom and Luke that end - I'm happy to help in any manner to ensure it goes in before.

>
> Also, what will be the guidelines for committing a change to 0.23
> branch? Is it "bug fix only" or are we still allowing improvements?
> Given how recently MR2 was merged, I imagine there will be a lot of
> things that aren't strictly bugs that we will really want to have in
> our next release. I also have a couple of HDFS patches (eg the new
> faster CRC on-by-default) that I'd like to get into 23.
>

There aren't strict policies - as far as I remember both Suresh and a certain Todd (know him? *smile*) volunteered to provide that oversight for HDFS, I don' t plan to be very strict. However, it will be a good policy to ask folks to justify why it belongs in 23, and we make a judgement call together.

Makes sense?

Arun

+1 for creating the branch. As I said earlier, I am willing to help with any
HDFS issues.

On Thu, Aug 18, 2011 at 1:28 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:

>
> On Aug 18, 2011, at 1:21 PM, Todd Lipcon wrote:
> >>
> >> I propose to do it noon of the coming Monday (Aug 22).
> >>
> >> Thoughts?
> >
> > I assume we will make sure the HDFS mavenization is in before then?
> > Tom said he intends to commit it tomorrow, but if something comes up
> > and it's not committed, let's make sure mavenization happens before we
> > branch.
>
> Yes, I assume it will be done too. I see a flurry of activity from
> Alejandro, Tom and Luke that end - I'm happy to help in any manner to ensure
> it goes in before.
>
> >
> > Also, what will be the guidelines for committing a change to 0.23
> > branch? Is it "bug fix only" or are we still allowing improvements?
> > Given how recently MR2 was merged, I imagine there will be a lot of
> > things that aren't strictly bugs that we will really want to have in
> > our next release. I also have a couple of HDFS patches (eg the new
> > faster CRC on-by-default) that I'd like to get into 23.
> >
>
> There aren't strict policies - as far as I remember both Suresh and a
> certain Todd (know him? *smile*) volunteered to provide that oversight for
> HDFS, I don' t plan to be very strict. However, it will be a good policy to
> ask folks to justify why it belongs in 23, and we make a judgement call
> together.
>
> Makes sense?
>
> Arun
>
>

+1. Lets get rolling on 0.23.0!

mahadev

On Aug 18, 2011, at 1:34 PM, Suresh Srinivas wrote:

> +1 for creating the branch. As I said earlier, I am willing to help with any
> HDFS issues.
>
> On Thu, Aug 18, 2011 at 1:28 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>
>>
>> On Aug 18, 2011, at 1:21 PM, Todd Lipcon wrote:
>>>>
>>>> I propose to do it noon of the coming Monday (Aug 22).
>>>>
>>>> Thoughts?
>>>
>>> I assume we will make sure the HDFS mavenization is in before then?
>>> Tom said he intends to commit it tomorrow, but if something comes up
>>> and it's not committed, let's make sure mavenization happens before we
>>> branch.
>>
>> Yes, I assume it will be done too. I see a flurry of activity from
>> Alejandro, Tom and Luke that end - I'm happy to help in any manner to ensure
>> it goes in before.
>>
>>>
>>> Also, what will be the guidelines for committing a change to 0.23
>>> branch? Is it "bug fix only" or are we still allowing improvements?
>>> Given how recently MR2 was merged, I imagine there will be a lot of
>>> things that aren't strictly bugs that we will really want to have in
>>> our next release. I also have a couple of HDFS patches (eg the new
>>> faster CRC on-by-default) that I'd like to get into 23.
>>>
>>
>> There aren't strict policies - as far as I remember both Suresh and a
>> certain Todd (know him? *smile*) volunteered to provide that oversight for
>> HDFS, I don' t plan to be very strict. However, it will be a good policy to
>> ask folks to justify why it belongs in 23, and we make a judgement call
>> together.
>>
>> Makes sense?
>>
>> Arun
>>
>>

+1

If there are any changes to do with Maven that need doing after the
branch is cut (e.g. in MapReduce), then they can be done in trunk and
backported to the branch if the RM (Arun) agrees.

Cheers,
Tom

On Thu, Aug 18, 2011 at 9:36 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
> Good morning!
>
> On Jul 13, 2011, at 3:39 PM, Arun C Murthy wrote:
>
>> It's looking like trunk is moving along rapidly - it's about time to start thinking of the next release to unlock all of the goodies there.
>>
>> As the RM, my current thinking is that after we merge NextGen MR (MR-279) and the HDFS-1073 branch into trunk we should be good to create the hadoop-0.23 branch.
>
> Since the last time we spoke (actually, since last night, in fact!) the world (trunk) has changed to accommodate our wishes... *smile*
>
> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's time to cut the 0.23 branch so that we can focus on testing and stabilizing a hadoop-0.23 release off that branch.
>
> I propose to do it noon of the coming Monday (Aug 22).
>
> Thoughts?
>
> thanks,
> Arun

On Aug 18, 2011, at 2:22 PM, Tom White wrote:

> +1
>
> If there are any changes to do with Maven that need doing after the
> branch is cut (e.g. in MapReduce), then they can be done in trunk and
> backported to the branch if the RM (Arun) agrees.
>

In my opinion, generally, changes to build infrastructure are low risk and worth putting in.

So, it's a long way of saying - yes, we need the maven changes for hadoop-mapreduce. :)

Arun

> Cheers,
> Tom
>
> On Thu, Aug 18, 2011 at 9:36 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>> Good morning!
>>
>> On Jul 13, 2011, at 3:39 PM, Arun C Murthy wrote:
>>
>>> It's looking like trunk is moving along rapidly - it's about time to start thinking of the next release to unlock all of the goodies there.
>>>
>>> As the RM, my current thinking is that after we merge NextGen MR (MR-279) and the HDFS-1073 branch into trunk we should be good to create the hadoop-0.23 branch.
>>
>> Since the last time we spoke (actually, since last night, in fact!) the world (trunk) has changed to accommodate our wishes... *smile*
>>
>> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's time to cut the 0.23 branch so that we can focus on testing and stabilizing a hadoop-0.23 release off that branch.
>>
>> I propose to do it noon of the coming Monday (Aug 22).
>>
>> Thoughts?
>>
>> thanks,
>> Arun

+1.  This is great news.

On Thu, Aug 18, 2011 at 2:26 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>
> On Aug 18, 2011, at 2:22 PM, Tom White wrote:
>
>> +1
>>
>> If there are any changes to do with Maven that need doing after the
>> branch is cut (e.g. in MapReduce), then they can be done in trunk and
>> backported to the branch if the RM (Arun) agrees.
>>
>
> In my opinion, generally, changes to build infrastructure are low risk and worth putting in.
>
> So, it's a long way of saying - yes, we need the maven changes for hadoop-mapreduce. :)
>
> Arun
>
>> Cheers,
>> Tom
>>
>> On Thu, Aug 18, 2011 at 9:36 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>> Good morning!
>>>
>>> On Jul 13, 2011, at 3:39 PM, Arun C Murthy wrote:
>>>
>>>> It's looking like trunk is moving along rapidly - it's about time to start thinking of the next release to unlock all of the goodies there.
>>>>
>>>> As the RM, my current thinking is that after we merge NextGen MR (MR-279) and the HDFS-1073 branch into trunk we should be good to create the hadoop-0.23 branch.
>>>
>>> Since the last time we spoke (actually, since last night, in fact!) the world (trunk) has changed to accommodate our wishes... *smile*
>>>
>>> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's time to cut the 0.23 branch so that we can focus on testing and stabilizing a hadoop-0.23 release off that branch.
>>>
>>> I propose to do it noon of the coming Monday (Aug 22).
>>>
>>> Thoughts?
>>>
>>> thanks,
>>> Arun
>
>

On Aug 18, 2011, at 9:36 AM, Arun C Murthy wrote:
> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's time to cut the 0.23 branch so that we can focus on testing and stabilizing a hadoop-0.23 release off that branch.
>
> I propose to do it noon of the coming Monday (Aug 22).

Reminder - I'll create the branch at noon today.

thanks,
Arun

Arun,

I think getting a stable build on trunk through jenkins before
branching 0.23 would be good.
common build issues are fixed. -
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-trunk/

I'm workin on hdfs and mapreduce build setup.

-Giri

On Mon, Aug 22, 2011 at 10:05 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>
> On Aug 18, 2011, at 9:36 AM, Arun C Murthy wrote:
>> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's time to cut the 0.23 branch so that we can focus on testing and stabilizing a hadoop-0.23 release off that branch.
>>
>> I propose to do it noon of the coming Monday (Aug 22).
>
> Reminder - I'll create the branch at noon today.
>
> thanks,
> Arun
>
>
>

Good point, I'll wait for your go ahead. Thanks for keeping on top of this!

On Aug 22, 2011, at 11:19 AM, Giridharan Kesavan wrote:

> Arun,
>
> I think getting a stable build on trunk through jenkins before
> branching 0.23 would be good.
> common build issues are fixed. -
> https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-trunk/
>
> I'm workin on hdfs and mapreduce build setup.
>
> -Giri
>
> On Mon, Aug 22, 2011 at 10:05 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>
>> On Aug 18, 2011, at 9:36 AM, Arun C Murthy wrote:
>>> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's time to cut the 0.23 branch so that we can focus on testing and stabilizing a hadoop-0.23 release off that branch.
>>>
>>> I propose to do it noon of the coming Monday (Aug 22).
>>
>> Reminder - I'll create the branch at noon today.
>>
>> thanks,
>> Arun
>>
>>
>>

+1 branching 0.23
Would be very good to stabilize Jenkins build before that.
--Konstantin

On Mon, Aug 22, 2011 at 11:19 AM, Giridharan Kesavan <
[EMAIL PROTECTED]> wrote:

> Arun,
>
> I think getting a stable build on trunk through jenkins before
> branching 0.23 would be good.
> common build issues are fixed. -
> https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-trunk/
>
> I'm workin on hdfs and mapreduce build setup.
>
> -Giri
>
> On Mon, Aug 22, 2011 at 10:05 AM, Arun C Murthy <[EMAIL PROTECTED]>
> wrote:
> >
> > On Aug 18, 2011, at 9:36 AM, Arun C Murthy wrote:
> >> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's time
> to cut the 0.23 branch so that we can focus on testing and stabilizing a
> hadoop-0.23 release off that branch.
> >>
> >> I propose to do it noon of the coming Monday (Aug 22).
> >
> > Reminder - I'll create the branch at noon today.
> >
> > thanks,
> > Arun
> >
> >
> >
>

+1 (not binding). IMO we should first take care of HADOOP-7560 (whatever is
the resolution) to easily merge patches.

On Tue, Aug 23, 2011 at 4:36 PM, Konstantin Shvachko
<[EMAIL PROTECTED]>wrote:

> +1 branching 0.23
> Would be very good to stabilize Jenkins build before that.
> --Konstantin
>
> On Mon, Aug 22, 2011 at 11:19 AM, Giridharan Kesavan <
> [EMAIL PROTECTED]> wrote:
>
> > Arun,
> >
> > I think getting a stable build on trunk through jenkins before
> > branching 0.23 would be good.
> > common build issues are fixed. -
> > https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-trunk/
> >
> > I'm workin on hdfs and mapreduce build setup.
> >
> > -Giri
> >
> > On Mon, Aug 22, 2011 at 10:05 AM, Arun C Murthy <[EMAIL PROTECTED]>
> > wrote:
> > >
> > > On Aug 18, 2011, at 9:36 AM, Arun C Murthy wrote:
> > >> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's
> time
> > to cut the 0.23 branch so that we can focus on testing and stabilizing a
> > hadoop-0.23 release off that branch.
> > >>
> > >> I propose to do it noon of the coming Monday (Aug 22).
> > >
> > > Reminder - I'll create the branch at noon today.
> > >
> > > thanks,
> > > Arun
> > >
> > >
> > >
> >
>

Yes, I'm waiting for the Jenkins build (Giri is working furiously on it) and HADOOP-7560 before the cutting the merge.

thanks,
Arun

On Aug 23, 2011, at 4:52 PM, Alejandro Abdelnur wrote:

> +1 (not binding). IMO we should first take care of HADOOP-7560 (whatever is
> the resolution) to easily merge patches.
>
> On Tue, Aug 23, 2011 at 4:36 PM, Konstantin Shvachko
> <[EMAIL PROTECTED]>wrote:
>
>> +1 branching 0.23
>> Would be very good to stabilize Jenkins build before that.
>> --Konstantin
>>
>> On Mon, Aug 22, 2011 at 11:19 AM, Giridharan Kesavan <
>> [EMAIL PROTECTED]> wrote:
>>
>>> Arun,
>>>
>>> I think getting a stable build on trunk through jenkins before
>>> branching 0.23 would be good.
>>> common build issues are fixed. -
>>> https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-trunk/
>>>
>>> I'm workin on hdfs and mapreduce build setup.
>>>
>>> -Giri
>>>
>>> On Mon, Aug 22, 2011 at 10:05 AM, Arun C Murthy <[EMAIL PROTECTED]>
>>> wrote:
>>>>
>>>> On Aug 18, 2011, at 9:36 AM, Arun C Murthy wrote:
>>>>> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's
>> time
>>> to cut the 0.23 branch so that we can focus on testing and stabilizing a
>>> hadoop-0.23 release off that branch.
>>>>>
>>>>> I propose to do it noon of the coming Monday (Aug 22).
>>>>
>>>> Reminder - I'll create the branch at noon today.
>>>>
>>>> thanks,
>>>> Arun
>>>>
>>>>
>>>>
>>>
>>

Thanks to help from Alejandro, Tom, Eric Yang and Mahadev, we have all the necessary build work safely in trunk.

I propose to branch noon tmrw (18/25), heads up.

thanks,
Arun

On Aug 23, 2011, at 5:21 PM, Arun C Murthy wrote:

> Yes, I'm waiting for the Jenkins build (Giri is working furiously on it) and HADOOP-7560 before the cutting the merge.
>
> thanks,
> Arun
>
> On Aug 23, 2011, at 4:52 PM, Alejandro Abdelnur wrote:
>
>> +1 (not binding). IMO we should first take care of HADOOP-7560 (whatever is
>> the resolution) to easily merge patches.
>>
>> On Tue, Aug 23, 2011 at 4:36 PM, Konstantin Shvachko
>> <[EMAIL PROTECTED]>wrote:
>>
>>> +1 branching 0.23
>>> Would be very good to stabilize Jenkins build before that.
>>> --Konstantin
>>>
>>> On Mon, Aug 22, 2011 at 11:19 AM, Giridharan Kesavan <
>>> [EMAIL PROTECTED]> wrote:
>>>
>>>> Arun,
>>>>
>>>> I think getting a stable build on trunk through jenkins before
>>>> branching 0.23 would be good.
>>>> common build issues are fixed. -
>>>> https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-trunk/
>>>>
>>>> I'm workin on hdfs and mapreduce build setup.
>>>>
>>>> -Giri
>>>>
>>>> On Mon, Aug 22, 2011 at 10:05 AM, Arun C Murthy <[EMAIL PROTECTED]>
>>>> wrote:
>>>>>
>>>>> On Aug 18, 2011, at 9:36 AM, Arun C Murthy wrote:
>>>>>> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's
>>> time
>>>> to cut the 0.23 branch so that we can focus on testing and stabilizing a
>>>> hadoop-0.23 release off that branch.
>>>>>>
>>>>>> I propose to do it noon of the coming Monday (Aug 22).
>>>>>
>>>>> Reminder - I'll create the branch at noon today.
>>>>>
>>>>> thanks,
>>>>> Arun
>>>>>
>>>>>
>>>>>
>>>>
>>>
>

FYI - I'm holding breath for one last patch (no pressure Mahadev/Tom ;)) and I'll branch right after.

thanks,
Arun

On Aug 24, 2011, at 5:27 PM, Arun C Murthy wrote:

> Thanks to help from Alejandro, Tom, Eric Yang and Mahadev, we have all the necessary build work safely in trunk.
>
> I propose to branch noon tmrw (18/25), heads up.
>
> thanks,
> Arun
>
> On Aug 23, 2011, at 5:21 PM, Arun C Murthy wrote:
>
>> Yes, I'm waiting for the Jenkins build (Giri is working furiously on it) and HADOOP-7560 before the cutting the merge.
>>
>> thanks,
>> Arun
>>
>> On Aug 23, 2011, at 4:52 PM, Alejandro Abdelnur wrote:
>>
>>> +1 (not binding). IMO we should first take care of HADOOP-7560 (whatever is
>>> the resolution) to easily merge patches.
>>>
>>> On Tue, Aug 23, 2011 at 4:36 PM, Konstantin Shvachko
>>> <[EMAIL PROTECTED]>wrote:
>>>
>>>> +1 branching 0.23
>>>> Would be very good to stabilize Jenkins build before that.
>>>> --Konstantin
>>>>
>>>> On Mon, Aug 22, 2011 at 11:19 AM, Giridharan Kesavan <
>>>> [EMAIL PROTECTED]> wrote:
>>>>
>>>>> Arun,
>>>>>
>>>>> I think getting a stable build on trunk through jenkins before
>>>>> branching 0.23 would be good.
>>>>> common build issues are fixed. -
>>>>> https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-trunk/
>>>>>
>>>>> I'm workin on hdfs and mapreduce build setup.
>>>>>
>>>>> -Giri
>>>>>
>>>>> On Mon, Aug 22, 2011 at 10:05 AM, Arun C Murthy <[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>>
>>>>>> On Aug 18, 2011, at 9:36 AM, Arun C Murthy wrote:
>>>>>>> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's
>>>> time
>>>>> to cut the 0.23 branch so that we can focus on testing and stabilizing a
>>>>> hadoop-0.23 release off that branch.
>>>>>>>
>>>>>>> I propose to do it noon of the coming Monday (Aug 22).
>>>>>>
>>>>>> Reminder - I'll create the branch at noon today.
>>>>>>
>>>>>> thanks,
>>>>>> Arun
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>
>

All clear, I'm starting the branch now. Please hold off your commits.

thanks,
Arun

On Aug 25, 2011, at 12:23 PM, Arun C Murthy wrote:

> FYI - I'm holding breath for one last patch (no pressure Mahadev/Tom ;)) and I'll branch right after.
>
> thanks,
> Arun
>
> On Aug 24, 2011, at 5:27 PM, Arun C Murthy wrote:
>
>> Thanks to help from Alejandro, Tom, Eric Yang and Mahadev, we have all the necessary build work safely in trunk.
>>
>> I propose to branch noon tmrw (18/25), heads up.
>>
>> thanks,
>> Arun
>>
>> On Aug 23, 2011, at 5:21 PM, Arun C Murthy wrote:
>>
>>> Yes, I'm waiting for the Jenkins build (Giri is working furiously on it) and HADOOP-7560 before the cutting the merge.
>>>
>>> thanks,
>>> Arun
>>>
>>> On Aug 23, 2011, at 4:52 PM, Alejandro Abdelnur wrote:
>>>
>>>> +1 (not binding). IMO we should first take care of HADOOP-7560 (whatever is
>>>> the resolution) to easily merge patches.
>>>>
>>>> On Tue, Aug 23, 2011 at 4:36 PM, Konstantin Shvachko
>>>> <[EMAIL PROTECTED]>wrote:
>>>>
>>>>> +1 branching 0.23
>>>>> Would be very good to stabilize Jenkins build before that.
>>>>> --Konstantin
>>>>>
>>>>> On Mon, Aug 22, 2011 at 11:19 AM, Giridharan Kesavan <
>>>>> [EMAIL PROTECTED]> wrote:
>>>>>
>>>>>> Arun,
>>>>>>
>>>>>> I think getting a stable build on trunk through jenkins before
>>>>>> branching 0.23 would be good.
>>>>>> common build issues are fixed. -
>>>>>> https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-trunk/
>>>>>>
>>>>>> I'm workin on hdfs and mapreduce build setup.
>>>>>>
>>>>>> -Giri
>>>>>>
>>>>>> On Mon, Aug 22, 2011 at 10:05 AM, Arun C Murthy <[EMAIL PROTECTED]>
>>>>>> wrote:
>>>>>>>
>>>>>>> On Aug 18, 2011, at 9:36 AM, Arun C Murthy wrote:
>>>>>>>> HDFS-1073 and MAPREDUCE-279 are presently in trunk and I think it's
>>>>> time
>>>>>> to cut the 0.23 branch so that we can focus on testing and stabilizing a
>>>>>> hadoop-0.23 release off that branch.
>>>>>>>>
>>>>>>>> I propose to do it noon of the coming Monday (Aug 22).
>>>>>>>
>>>>>>> Reminder - I'll create the branch at noon today.
>>>>>>>
>>>>>>> thanks,
>>>>>>> Arun
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>
>>
>

+1   Thanks for all the hard work.

To confirm, all changes will still still flow through trunk first?
We'll be able to merge HDFS-1623 in some update?

Thanks,
Eli

On Wed, Jul 13, 2011 at 3:39 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
> Hi All,
>
>  It's looking like trunk is moving along rapidly - it's about time to start thinking of the next release to unlock all of the goodies there.
>
>  As the RM, my current thinking is that after we merge NextGen MR (MR-279) and the HDFS-1073 branch into trunk we should be good to create the hadoop-0.23 branch.
>
>  Thoughts?
>
> thanks,
> Arun

On Thu, Aug 18, 2011 at 2:16 PM, Eli Collins <[EMAIL PROTECTED]> wrote:
> +1   Thanks for all the hard work.
>
> To confirm, all changes will still still flow through trunk first?
> We'll be able to merge HDFS-1623 in some update?
Ping.   Arun, can you confirm?

Thanks,
Eli

Sorry, missed the original.

As I had indicated previously, I'm fine with that.

thanks,
Arun

On Aug 19, 2011, at 11:47 AM, Eli Collins <[EMAIL PROTECTED]> wrote:

> On Thu, Aug 18, 2011 at 2:16 PM, Eli Collins <[EMAIL PROTECTED]> wrote:
>> +1   Thanks for all the hard work.
>>
>> To confirm, all changes will still still flow through trunk first?
>> We'll be able to merge HDFS-1623 in some update?
>
>
> Ping.   Arun, can you confirm?
>
> Thanks,
> Eli

On Wed, Jul 13, 2011 at 3:39 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
> Hi All,
>
>  It's looking like trunk is moving along rapidly - it's about time to start thinking of the next release to unlock all of the goodies there.
>
>  As the RM, my current thinking is that after we merge NextGen MR (MR-279) and the HDFS-1073 branch into trunk we should be good to create the hadoop-0.23 branch.
>
>  Thoughts?
>

Sounds great.

In order to support HA in a dot release we'll need to merge in the
branch for HDFS-1623, but that shouldn't hold up branching for 23.
Sanjay mentioned this as the summit but I wanted to double check with
you, you support a dot release of 23 with HA? The hope is that we
support one of the multiple options HDFS-1623 allows for, and that we
introduce an incompatible change only when absolutely necessary.

If that doesn't work for you we could do a 0.24 release for HA but the
hope is that we'll get more people contributing to this release.

Thanks,
Eli

On Jul 13, 2011, at 6:01 PM, Eli Collins wrote:

> On Wed, Jul 13, 2011 at 3:39 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>> Hi All,
>>
>>  It's looking like trunk is moving along rapidly - it's about time to start thinking of the next release to unlock all of the goodies there.
>>
>>  As the RM, my current thinking is that after we merge NextGen MR (MR-279) and the HDFS-1073 branch into trunk we should be good to create the hadoop-0.23 branch.
>>
>>  Thoughts?
>>
>
> Sounds great.
>
> In order to support HA in a dot release we'll need to merge in the
> branch for HDFS-1623, but that shouldn't hold up branching for 23.
> Sanjay mentioned this as the summit but I wanted to double check with
> you, you support a dot release of 23 with HA? The hope is that we
> support one of the multiple options HDFS-1623 allows for, and that we
> introduce an incompatible change only when absolutely necessary.
>

+1

I'd strongly be in favour of a dot release of 0.23 with HA - this would be a step forward for Hadoop.

Let's discuss the specifics a little longer down the road once HA is further along? Makes sense?

thanks,
Arun

On Wed, Jul 13, 2011 at 6:10 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>
> On Jul 13, 2011, at 6:01 PM, Eli Collins wrote:
>
>> On Wed, Jul 13, 2011 at 3:39 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>> Hi All,
>>>
>>>  It's looking like trunk is moving along rapidly - it's about time to start thinking of the next release to unlock all of the goodies there.
>>>
>>>  As the RM, my current thinking is that after we merge NextGen MR (MR-279) and the HDFS-1073 branch into trunk we should be good to create the hadoop-0.23 branch.
>>>
>>>  Thoughts?
>>>
>>
>> Sounds great.
>>
>> In order to support HA in a dot release we'll need to merge in the
>> branch for HDFS-1623, but that shouldn't hold up branching for 23.
>> Sanjay mentioned this as the summit but I wanted to double check with
>> you, you support a dot release of 23 with HA? The hope is that we
>> support one of the multiple options HDFS-1623 allows for, and that we
>> introduce an incompatible change only when absolutely necessary.
>>
>
> +1
>
> I'd strongly be in favour of a dot release of 0.23 with HA - this would be a step forward for Hadoop.
>
> Let's discuss the specifics a little longer down the road once HA is further along? Makes sense?
>

Excellent.  Sounds good.

Thanks,
Eli

On Jul 13, 2011, at 6:01 PM, Eli Collins wrote:
>
> In order to support HA in a dot release we'll need to merge in the
> branch for HDFS-1623, but that shouldn't hold up branching for 23.
> Sanjay mentioned this as the summit but I wanted to double check with
> you, you support a dot release of 23 with HA?

Please don't do this.  0.23 is a MASSIVE change.  Introducing even more instability in the form of a new major feature in the middle of a release that is bound to be full of problems is not a good idea.   Anyone who runs a production system will basically ignore 0.23 because it simply won't be stable enough.  (It *always* takes a .1 or .2 or even a .3 before things are actually rock solid.)

I'd much rather see 0.24 have HA than 0.23.