There are six +1s (Mahadev, Eli, Suresh, Arun, Jitendra and myself) and no -1s.  The vote passed.

I will send out emails to the dev mailing lists right before the merging.

Thanks everyone!

Tsz-Wo Nicholas Sze
Hortonworks Inc.
http://hortonworks.com/
________________________________
From: "Tsz Wo (Nicholas), Sze" <[EMAIL PROTECTED]>
To: general hadoop <[EMAIL PROTECTED]>
Sent: Wednesday, February 22, 2012 4:02 PM
Subject: [VOTE] Merging 0.23-PB to 0.23

We actually require to have a vote according to the bylaws (Thanks Aaron Myers for the kindly note.)  Please check the branch and vote.

Tsz-Wo Nicholas Sze
Hortonworks Inc.
http://hortonworks.com/
________________________________
From: Mahadev Konar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; "Tsz Wo (Nicholas), Sze" <[EMAIL PROTECTED]>
Sent: Wednesday, February 22, 2012 3:30 PM
Subject: Re: Merging 0.23-PB to 0.23

Sounds great! +1 for merging. Would be good to get this into 0.23
branch as soon as possible.

Mahadev Konar
Hortonworks Inc.
http://hortonworks.com/
On Wed, Feb 22, 2012 at 12:20 PM, Tsz Wo (Nicholas), Sze
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> The IPC protocol buffer feature in trunk is complete.  It is time to merge 0.23-PB back to 0.23.  Lists of 0.23-PB issues which are not in 0.23 can be found in the CHANGES.txt files in the 0.23-PB branch.  I will merge it tomorrow.  Please let me know if you have any concern.
>
> Regards,
>
> Tsz-Wo Nicholas Sze
> Hortonworks Inc.
> http://hortonworks.com/

Neat.

Based on the previous discussion, I've created a branch-0.23.2 and set version on branch-0.23 to be 0.23.3. You are good to go there.

thanks,
Arun

On Feb 24, 2012, at 4:01 PM, Tsz Wo (Nicholas), Sze wrote:

> There are six +1s (Mahadev, Eli, Suresh, Arun, Jitendra and myself) and no -1s.  The vote passed.
>
> I will send out emails to the dev mailing lists right before the merging.
>
> Thanks everyone!
>
> Tsz-Wo Nicholas Sze
> Hortonworks Inc.
> http://hortonworks.com/
>
>
> ________________________________
> From: "Tsz Wo (Nicholas), Sze" <[EMAIL PROTECTED]>
> To: general hadoop <[EMAIL PROTECTED]>
> Sent: Wednesday, February 22, 2012 4:02 PM
> Subject: [VOTE] Merging 0.23-PB to 0.23
>
> We actually require to have a vote according to the bylaws (Thanks Aaron Myers for the kindly note.)  Please check the branch and vote.
>
> Tsz-Wo Nicholas Sze
> Hortonworks Inc.
> http://hortonworks.com/
>
>
> ________________________________
> From: Mahadev Konar <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]; "Tsz Wo (Nicholas), Sze" <[EMAIL PROTECTED]>
> Sent: Wednesday, February 22, 2012 3:30 PM
> Subject: Re: Merging 0.23-PB to 0.23
>
> Sounds great! +1 for merging. Would be good to get this into 0.23
> branch as soon as possible.
>
> Mahadev Konar
> Hortonworks Inc.
> http://hortonworks.com/
>
>
> On Wed, Feb 22, 2012 at 12:20 PM, Tsz Wo (Nicholas), Sze
> <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> The IPC protocol buffer feature in trunk is complete.  It is time to merge 0.23-PB back to 0.23.  Lists of 0.23-PB issues which are not in 0.23 can be found in the CHANGES.txt files in the 0.23-PB branch.  I will merge it tomorrow.  Please let me know if you have any concern.
>>
>> Regards,
>>
>> Tsz-Wo Nicholas Sze
>> Hortonworks Inc.
>> http://hortonworks.com/

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

On 25/02/12 02:01, Arun C Murthy wrote:
> Neat.
>
> Based on the previous discussion, I've created a branch-0.23.2 and set version on branch-0.23 to be 0.23.3. You are good to go there.

OK, there are also JIRA version numbers for 0.23.3; I added a couple &
someone had already stuck one in for MAPREDUCE

On 25/02/12 02:01, Arun C Murthy wrote:
> Neat.
>
> Based on the previous discussion, I've created a branch-0.23.2 and set version on branch-0.23 to be 0.23.3. You are good to go there.
>

to clarify this, anything I do on trunk that I want to get into the
0.23.x release should still be on branch-0.23? The 0.23.2 is
specifically for the followup to the 0.23.1 release that's just been
voted through, and is locked down for all changes except by the release
manager -you- ?