Release Management/Feature Uplift: Difference between revisions

Release Management/Feature Uplift (view source)

38 bytes added , 22 September 2014

Confirmed users

2,473

edits

@@ Line 2: / Line 2: @@
 In most cases new feature work should land on mozilla-central (m-c / Nightly). There may be cases when we choose to uplift a feature to Aurora or Beta. This document includes information to help guide the uplift decision and concerns that should be addressed before uplift.
-Note that for simple, isolated features, uplift can generally be handled by having a short conversation with the release manager for the release.
+Note that for simple, isolated features, uplift can generally be handled by having a short conversation with the [[Release_Management/Release_owners|release manager for the release]].
 == Why uplift ==
 The Firefox release process has been designed to balance new feature work and quality. Uplifting a feature subverts this process and reduces the amount of stabilization time available for the feature. Before uplifting a feature it is good to stop and ask why the feature needs to release sooner than the regular process allows.