ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jayush Luniya <jlun...@hortonworks.com>
Subject Re: Missed commit to 2.2.2 branch
Date Wed, 20 Apr 2016 19:03:24 GMT
The branch was created on 4/13. All, please verify that your commits are
in.
Thanks
Jayush


On 4/13/16, 5:02 PM, "Srimanth Gunturi" <sgunturi@hortonworks.com> wrote:

>Hello,
>The new branch 'branch-2.2.2' has been created for Ambari-2.2.2.
>
>An RC will be created soon after so we (as a team) should only accept
>patches for blocker issues only. If you have any doubts whether a fix
>should be committed into branch-2.2.2, please email me for input at
>sgunturi@hortonworks.com.
>
>Also, any commits for 'branch-2.2.2' should also be applied to
>'branch-2.2' and 'trunk'.?
>Best regards,
>Srimanth
>
>
>
>________________________________
>From: Srimanth Gunturi
>Sent: Wednesday, April 13, 2016 9:17 AM
>To: Ambari
>Subject: Preparing Ambari 2.2.2 branch
>
>
>?Hello,
>
>Working towards the goal of releasing Ambari-2.2.2, I am proposing
>cutting a new branch 'branch-2.2.2' today.
>
>After making the branch, we (i.e., development community) should only
>accept blocker ?or very critical bug fixes into the branch and harden it
>until it meets a high enough quality bar. If you have a bug fix, it
>should first be committed to trunk, and after ensuring that it does not
>break any tests (including smoke tests), then it should be integrated to
>the Ambari branch-2.2.2.
>
>Stay tuned for updates on the Ambari 2.2.2 release process.
>Best regards,
>Srimanth



On 4/20/16, 11:58 AM, "Alejandro Fernandez" <afernandez@hortonworks.com>
wrote:

>When was branch-2.2.2 created? I thought that release 2.2.2 was coming
>from commits to branch-2.2
>I want to make sure no commits were missed.
>
>Thanks,
>Alejandro
>
>On 4/20/16, 7:30 AM, "Dmitro Lysnichenko" <dlysnichenko@hortonworks.com>
>wrote:
>
>>Hi all,
>>
>>Some time ago I've committed patch for
>>https://issues.apache.org/jira/browse/AMBARI-15911 to trunk &
>>branch-2.2, but was not aware about branch-2.2.2. That's why committed
>>patch to this branch as well.
>>
>>Thanks,
>>Dmitro
>>
>>
>
>


Mime
View raw message