Team… The new branch (branch-2.2.1) has been created. You can now start committing code for 2.2.2 to branch-2.2.0.
Remember, 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.1, please email me for input at [email protected]. Also, any commits for branch-2.2.1 should also be applied to branch-2.2 and trunk. Thanks, Rob On 1/25/16, 8:58 AM, "Robert Levas" <[email protected]> wrote: >Team… > >I am getting ready to create the new branch. Please refrain from committing >to branch-2.2 until further notice. > >Thanks, > >Rob > > > > >On 1/21/16, 9:20 AM, "Robert Levas" <[email protected]> wrote: > >>Team, >> >>Sorry for the late notice. We are preparing to create a release candidate >>for Ambari 2.2.1. In an effort to ensure only the relevant code changes make >>it into this release, I plan to create a new branch (branch-2.2.1, using >>branch-2.2.0) on Monday, 1/25, around 9am EST. >> >>After this branch has been created, 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.1, please email >>me for input at [email protected]. >> >>If you have a patch that is to be committed, make sure it is committed to the >>trunk first and then to the branch. Also, make sure that any patches do not >>break any unit tests. So please run all unit tests before committing. >> >>Please let me know if you have any questions or concerns. >> >>Thanks, >> >>Rob >> >> >>
