287
edits
Changes
remove aurora section
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 branchesbranch.
All [https://developer.mozilla.org/en-US/docs/Developer_Guide/How_to_Submit_a_Patch regular guidelines] for changes apply.
=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 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'')
= Firefox (Desktop and Mobile) =
==Aurora Beta Uplift (approval-mozilla-aurorabeta)==* 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
* Ideally reproducible by QA so easily verified
* Has 'baked' on m-c/aurora and demonstrated decrease in crash or reproducibility
* No string changes
Changes can be:
