Release Management/Feature Uplift: Difference between revisions

Release Management/Feature Uplift (view source)

2 bytes added , 23 September 2014

no edit summary

Confirmed users

976

edits

@@ Line 15: / Line 15: @@
 * hard code strings and ship an English only feature - this is not generally acceptable but may be suitable in some cases
 ;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 (Jorge Villalobos) should be consulted for communicating the change 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 marking and comms plan. Work with these teams early to develop the plan.
+;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.
 ;Informing others: It will likely be beneficial to inform other teams of the uplift. You are encouraged to do so via a post to [https://lists.mozilla.org/listinfo/dev-platform dev-platform] and by discussing the uplift during the [[Platform/#Meetings|Engineering meeting]].