Changes

Jump to: navigation, search

Release Management/Uplift rules

1,281 bytes added, 00:18, 30 January 2014
Draft
'''This document is a draft.'''

This page describes the rules applied by the Release Team to uplift a patch in one of the release.
All regular guidelines for changes apply https://developer.mozilla.org/en-US/docs/Developer_Guide/How_to_Submit_a_Patch

=Aurora Uplift (approval-mozilla-aurora)=
* 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
* No 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
* Performance improvement (proven, need real numbers !!),top-crashers, recent regressions
* No string changes
* No changes to UUID in .idl files (will break addon compatibility)

=Release Uplift=
* Must be a part of a known-issue respin (what is respin) or NPTOB (not part of the build) config changes needed to support build infra

=Security fixes=
https://wiki.mozilla.org/Security/Bug_Approval_Process
Confirm
709
edits

Navigation menu