Release Management/Feature Uplift: Difference between revisions

Release Management/Feature Uplift (view source)

79 bytes added , 24 September 2014

Confirmed users

2,473

edits

@@ Line 20: / Line 20: @@
 == 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. Another option is to build the feature so that it can be disabled with <code>ifdef</code> statements.
+;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>[https://developer.mozilla.org/en-US/docs/When_To_Use_ifdefs#_Feature_ifdefs_ 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).
 ; Quality Engineering (QE) agreement: Acknowledgement from QE that they can test the feature and preferably a test plan.