4.4.1 related checkins

[Amogh Vasekar <am...@citrix.com>]

Hi,

I am wondering where we are to check-in commits we think should go in
4.4.1.
4.4 / 4.4-forward / create 4.4.1 / create a branch and request a merge /
some other way?

Thanks,
Amogh 

Re: 4.4.1 related checkins

[Daan Hoogland <da...@gmail.com>]

Amogh, make that branchname 'hotfix/4.4-' + jira ticket number. That
will trigger an automatic build due to some great work of our jenkins
adminstrator.

On Tue, Aug 5, 2014 at 9:23 AM, Daan Hoogland <da...@gmail.com> wrote:
> If it is trivial, make it on 4.4. If it needs review and testing make
> it on it's own branch. Name it something like fix-4.4-<ticketnumber>
> and have the RM merge it after validation.
>
> Please note that this is a way of working extracted from the new
> workflow but not exactly the same.
>
> thanks,
> your latest RM (we are looking for a 4.5 RM!)
>
> On Mon, Aug 4, 2014 at 11:59 PM, Amogh Vasekar <am...@citrix.com> wrote:
>> Hi,
>>
>> I am wondering where we are to check-in commits we think should go in
>> 4.4.1.
>> 4.4 / 4.4-forward / create 4.4.1 / create a branch and request a merge /
>> some other way?
>>
>> Thanks,
>> Amogh
>>
>
>
>
> --
> Daan



-- 
Daan

Re: 4.4.1 related checkins

[Daan Hoogland <da...@gmail.com>]

If it is trivial, make it on 4.4. If it needs review and testing make
it on it's own branch. Name it something like fix-4.4-<ticketnumber>
and have the RM merge it after validation.

Please note that this is a way of working extracted from the new
workflow but not exactly the same.

thanks,
your latest RM (we are looking for a 4.5 RM!)

On Mon, Aug 4, 2014 at 11:59 PM, Amogh Vasekar <am...@citrix.com> wrote:
> Hi,
>
> I am wondering where we are to check-in commits we think should go in
> 4.4.1.
> 4.4 / 4.4-forward / create 4.4.1 / create a branch and request a merge /
> some other way?
>
> Thanks,
> Amogh
>



-- 
Daan