You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by Andrew Purtell <ap...@apache.org> on 2014/08/21 20:11:48 UTC
[VOTE] Rename versioned branches after the next release set (3.1/4.1)
I propose the following actions be taken after the next release set (3.1
and 4.1)
- Create a new ref 'branch-3' pointing at the current head of '3.0'
- Delete the ref '3.0'
- Create a new ref 'branch-4' pointing at the current head of '4.0'
- Delete the ref '4.0'
- Push the above changes as:
git push asf branch-3 branch-4 :3.0 :4.0
- Update Jenkins builds
- Update documentation
Let's run this vote for 72 hours, 3 +1s from PMC to pass.
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: [VOTE] Rename versioned branches after the next release set (3.1/4.1)
Posted by James Taylor <ja...@apache.org>.
+1
On Thu, Aug 21, 2014 at 11:13 AM, Jesse Yates <je...@gmail.com> wrote:
> +1
>
> -------------------
> Jesse Yates
> @jesse_yates
> jyates.github.com
>
>
> On Thu, Aug 21, 2014 at 11:11 AM, Andrew Purtell <ap...@apache.org>
> wrote:
>
>> I propose the following actions be taken after the next release set (3.1
>> and 4.1)
>>
>> - Create a new ref 'branch-3' pointing at the current head of '3.0'
>>
>> - Delete the ref '3.0'
>>
>> - Create a new ref 'branch-4' pointing at the current head of '4.0'
>>
>> - Delete the ref '4.0'
>>
>> - Push the above changes as:
>>
>> git push asf branch-3 branch-4 :3.0 :4.0
>>
>> - Update Jenkins builds
>>
>> - Update documentation
>>
>> Let's run this vote for 72 hours, 3 +1s from PMC to pass.
>>
>> --
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
Re: [VOTE] Rename versioned branches after the next release set (3.1/4.1)
Posted by Jesse Yates <je...@gmail.com>.
+1
-------------------
Jesse Yates
@jesse_yates
jyates.github.com
On Thu, Aug 21, 2014 at 11:11 AM, Andrew Purtell <ap...@apache.org>
wrote:
> I propose the following actions be taken after the next release set (3.1
> and 4.1)
>
> - Create a new ref 'branch-3' pointing at the current head of '3.0'
>
> - Delete the ref '3.0'
>
> - Create a new ref 'branch-4' pointing at the current head of '4.0'
>
> - Delete the ref '4.0'
>
> - Push the above changes as:
>
> git push asf branch-3 branch-4 :3.0 :4.0
>
> - Update Jenkins builds
>
> - Update documentation
>
> Let's run this vote for 72 hours, 3 +1s from PMC to pass.
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
Re: [VOTE] Rename versioned branches after the next release set (3.1/4.1)
Posted by Nick Dimiduk <nd...@gmail.com>.
+1
On Thu, Aug 21, 2014 at 11:11 AM, Andrew Purtell <ap...@apache.org>
wrote:
> I propose the following actions be taken after the next release set (3.1
> and 4.1)
>
> - Create a new ref 'branch-3' pointing at the current head of '3.0'
>
> - Delete the ref '3.0'
>
> - Create a new ref 'branch-4' pointing at the current head of '4.0'
>
> - Delete the ref '4.0'
>
> - Push the above changes as:
>
> git push asf branch-3 branch-4 :3.0 :4.0
>
> - Update Jenkins builds
>
> - Update documentation
>
> Let's run this vote for 72 hours, 3 +1s from PMC to pass.
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>