Hi developers and PMCs,

I am proposing cutting the branch for Ambari 1.7.0 on Friday October 3 at 2
pm Pacific Time, as per the outlined tasks in the Ambari Feature + Roadmap
page (
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=30755705).

After making the branch, we (i.e., development community) should only
accept blocker or critical bug fixes into the branch and harden it until it
meets a high enough quality bar (roughly around 4 weeks, and subject to
change).
To further improve the stability of the release branch, we will require all
checkins into Ambari 1.7.0 to be reviewed by at least two committers and
unit-tested & system-tested.

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 1.7.0 branch.

If you have any doubts whether a fix should be committed into the 1.7.0
branch, please email me for input at [email protected]

Stay tuned for updates on the release process.

Thank you,
Alejandro Fernandez
Ambari 1.7.0 Release Manager

Reply via email to