Confirmed users
2,473
edits
Release Management/Feature Uplift: Difference between revisions
Release Management/Feature Uplift (view source)
Revision as of 19:59, 22 September 2014
, 22 September 2014→Approval
| Line 26: | Line 26: | ||
== Approve / Inform == | == Approve / Inform == | ||
=== Approval === | === Approval === | ||
;Release Manager: The release manager for the release is the decision maker for uplift. | ;Release Manager: The [[Release_Management/Release_owners|release manager for the release]] is the decision maker for uplift. | ||
;Firefox Senior Management: For a substantial, user facing desktop feature, Gavin Sharp, Madhava Enros, and Chad Weiner should sign off on the uplift. | ;Firefox Senior Management: For a substantial, user facing desktop feature, Gavin Sharp, Madhava Enros, and Chad Weiner should sign off on the uplift. | ||
;Fennec Senior Management: For a substantial, user facing mobile feature, Mark Finkle, Brad Lassey, and Karen Rudnitski should sign off on the uplift. | ;Fennec Senior Management: For a substantial, user facing mobile feature, Mark Finkle, Brad Lassey, and Karen Rudnitski should sign off on the uplift. | ||
Note: In cases of disagreement where an escalation is required, Johnathan Nightingale, VP Firefox, will be the ultimate decision maker. | Note: In cases of disagreement where an escalation is required, Johnathan Nightingale, VP Firefox, will be the ultimate decision maker. | ||
=== Inform === | === Inform === | ||
;Quality Engineering (QE): The QE release lead for the release is responsible for developing test plans and testing the feature. They should be consulted on the uplift. | ;Quality Engineering (QE): The QE release lead for the release is responsible for developing test plans and testing the feature. They should be consulted on the uplift. | ||