Confirmed users
2,473
edits
Release Management/Feature Uplift: Difference between revisions
Jump to navigation
Jump to search
Release Management/Feature Uplift (view source)
Revision as of 20:39, 22 September 2014
, 22 September 2014→Requirements for uplift
| Line 19: | Line 19: | ||
== Requirements for uplift == | == Requirements for uplift == | ||
;Ability to pref off: With less time to stabilize the feature, we need the ability to disable it quickly if the need arises. This is most easily accomplished by creating a pref to disable the feature. | ;Ability to pref off: With less time to stabilize the feature, we need the ability to disable it quickly if the need arises. This is most easily accomplished by creating a pref to disable the feature. Another option is to build the feature so that it can be disabled with <code>ifdef</code> statements. | ||
; Automated tests: Automated tests are required before uplifting the feature. The point is to prove to the best of our ability that the feature is stable before landing it on one of our stabilization branches (Aurora and Beta). | ; Automated tests: Automated tests are required before uplifting the feature. The point is to prove to the best of our ability that the feature is stable before landing it on one of our stabilization branches (Aurora and Beta). | ||
; Quality Engineering (QE) agreement: Acknowledgement from QE that they can test the feature and preferably a test plan. | ; Quality Engineering (QE) agreement: Acknowledgement from QE that they can test the feature and preferably a test plan. | ||