Release Management/Uplift rules: Difference between revisions

Release Management/Uplift rules (view source)

Revision as of 16:07, 16 October 2017

693 bytes removed , 16 October 2017

remove aurora section

Julien Cristau

297

edits

@@ Line 1: / Line 1: @@
-This page describes the rules applied by the Release Team to uplift (aka backport) a patch from a development branch to a more stable branch. For example, taking a patch that fixes a bug in Nightly and applying it to the aurora and beta branches.
+This page describes the rules applied by the Release Team to uplift (aka backport) a patch from a development branch to a more stable branch. For example, taking a patch that fixes a bug in Nightly and applying it to the beta branch.
 All [https://developer.mozilla.org/en-US/docs/Developer_Guide/How_to_Submit_a_Patch regular guidelines] for changes apply.
@@ Line 7: / Line 7: @@
 =General=
 * Uplifts are requested in the ''Details'' page of the attachment, ''Flags'' section which should be updated.
-* If a patch is considered as risky and impact both aurora and beta, please make sure that the other responsible is aware of the uplift.
+* If a patch is considered as risky and impacts beta, please make sure that the other responsible is aware of the uplift.
 * For a risky patch, don't hesitate to set the keyword "verifyme" to make sure someone will check if the bug is actually fixed.
 * The name/nickname of the release manager who approved the uplift will be added in the commit message with ''a='' (example: ''a=foobar'')
@@ Line 24: / Line 24: @@
 = Firefox (Desktop and Mobile) =
-==Aurora Uplift (approval-mozilla-aurora)==
+==Beta Uplift (approval-mozilla-beta)==
-* Can accept IDL (with UUID bump)  changes as we do not lock down binary for addons until Beta
-* No string changes unless late-l10n awareness and OK given
 * Must be landed on mozilla-central, or reason given for direct-to-branch uplift
-* No new feature landing
-* No disruptive important refactoring
-* No massive code changes
-==Beta Uplift (approval-mozilla-beta)==
-* Must be landed on mozilla-central as well as mozilla-aurora, or reason given for direct-to-branch uplift
 * Ideally reproducible by QA so easily verified
-* Has 'baked' on m-c/aurora and demonstrated decrease in crash or reproducibility
+* Has 'baked' on m-c and demonstrated decrease in crash or reproducibility
 * No string changes
-* No changes to UUID in .idl files (will break addon compatibility)  (This is no longer true; additions to an IDL would only cause problems for add-ons using binary XPCOM, which we no longer support)  Do we have any restrictions left for uuid changes on beta?
 Changes can be: