Release Management/Feature Uplift: Difference between revisions

Release Management/Feature Uplift (view source)

73 bytes added , 24 September 2014

Confirmed users

2,473

edits

@@ Line 12: / Line 12: @@
 == Considerations for uplift ==
 ;Localization (l10n): No string changes are permitted on Aurora and Beta without agreement from l10n. Every effort should be made to maintain string freeze on these branches so as to minimize the impact on the l10n teams. If a feature requires string changes, the [[L10n:Communication|l10n team]] must review before uplift.
-;UUID changes: UUID changes are acceptable on Aurora but generally not accepted on Beta (because they may break add-ons). If a feature requires UUID changes and uplift to Beta, the add-ons team (addons-team at mozilla dot com) should be consulted for communicating the change to add-on developers.
+;UUID changes: UUID changes are acceptable on Aurora but not acceptable on Beta (because they may break add-ons). If a feature requires UUID changes and uplift to Beta, the add-ons team (addons-team at mozilla dot com) should be consulted for assessing the impact to add-ons. If an exception to this rule is granted, the change must be communicated to add-on developers.
 ;Marketing and Comms plan:If there is a reason for uplifting a feature, the feature should typically be accompanied by a marketing and comms plan. Work with these teams early to develop the plan.
 ;Uplift landings: If the feature is sufficiently complex, it may be preferable to have the lead engineer land the changes on all branches themselves vs relying on the sheriffs for uplift.