Release Management/Uplift rules: Difference between revisions

Release Management/Uplift rules (view source)

35 bytes removed , 9 June 2014

Confirmed users

976

edits

@@ Line 52: / Line 52: @@
 ==approval-gaia-v2.0==
-* As we've moved on from active feature development to stabilization mode on 3/14 for the 1.4 Release, we understand that their may be issues that don't necessarily block but can make a strong case for uplifts (refer to the criteria below).
+* As we've moved on from active feature development to stabilization mode on 6/9 for the 2.0 Release, we understand that their may be issues that don't necessarily block but can make a strong case for uplifts (refer to the criteria below).
 * For such cases, we request folks to request approvals, which may be granted depending on the risk/reward analysis
 * Please note, the closer we try to wrap up stabilization mode the more stricter we'd be on taking any non-needed changes and absolutely no changes in the last sprint of stabilization
 === Criteria to request approval (Guidelines) ===
+* Patch must be landed and Resolved on master
 * any non-blocking bug that has a high user impact
 * a low risk Polish change : Visual polish - colors, sizes, icons, alignment, etc
@@ Line 62: / Line 63: @@
 * If you a requesting approval on a gaia patch that needs to land on 2.0 that
 ** Set approval-gaia-v2.0: ? and making sure to fill the populated set of questions [Approval Request Comment] that come up on the attachment
-** Note, for v2.0 - Non-blocking gaia approvals will not be approved after 4/11
 [[File:Gaia-approval.png|800px|center]]