Release Management/Feature Uplift: Difference between revisions

Line 17: Line 17:
;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 marking 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.
;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]].


== Requirements for uplift ==
== Requirements for uplift ==
Confirmed users
2,473

edits