Release Management/Process coordination for handling off-train releases: Difference between revisions

← Older edit

Release Management/Process coordination for handling off-train releases (view source)

Revision as of 15:25, 20 March 2025

1,526 bytes added , 20 March

Mark as obsolete

Pascalc

Confirmed users

1,311

edits

@@ Line 1: / Line 1: @@
+{{RELEASE_MANAGEMENT_OBSOLETE}}
+<p>The bulk of this information is available in [https://docs.google.com/document/d/13EU2B4hqt9x7z4g5ApF0AEWMPBpFPnrSf6dQ6kuEePM/ Ways to ship a change to Firefox Desktop] document.
+<br><br>
 = Goal =
@@ Line 8: / Line 13: @@
 The list of off-train release requests include (but are not limited to):
+* Shipping content via Remote Settings
 * Shipping a new Mozilla webextension
 * [https://wiki.mozilla.org/Firefox/Go_Faster/System_Add-ons/Process GoFaster] for shipping new system add-ons
@@ Line 38: / Line 44: @@
 | align=center| '''Checklist'''
 |- style="border:1pt solid #000000;padding:0.176cm;"
+| align=center| Content sent via Remote Settings
+|| Publishing content to Firefox users with the in-product messaging system (Remote Settings)
+''Example:'' (TBD)
+<u>Typical time-to-ship</u>: (TBD)
+|| Product manager/Dev owner files a bug and adds the messaging-system-request flag, filling out the resulting Bugzilla comment form.
+<u>Driver</u>: Product owner
+|| ✅ Product owner
+✅ Publishing engineer
+✅ Messaging (Firefox) Engineering peer
+✅ Messaging Product owner
+✅ Relman owner
+||[https://docs.google.com/document/d/1TAu5OQ_hWZjfL4k9-b7uEcjjyvWhgeQQD6X5ksCC7bc/edit#heading=h.rfqkfzwwckon Messaging system intake and release process]
+|- style="border:1pt solid #000000;padding:0.176cm;"
 | align=center| New Mozilla webext
 || A business need to publish Mozilla owned webext to Firefox Desktop users via AMO.
@@ Line 59: / Line 89: @@
-|| TODO add a link to a template for the process
+||
 |- style="border:1pt solid #000000;padding:0.176cm;"
 | align=center| GoFaster
@@ Line 212: / Line 242: @@
 = General process =
-As all these processes are similar, the general process is describe. Specificities are described in dedicated checklists.
+As all these processes are similar, the general process is described. Specific details are described in dedicated checklists.
 # Kick-off email thread or meeting to establish scope, owners and timeline.
@@ Line 226: / Line 256: @@
 # Publication of the change
 # QA sign off of the publication of the change
+= Process: Messaging to users with Remote Settings =
+==Decisions==
+== Extra steps ==
+== Checklist ==
+== Extra information ==
+[https://docs.google.com/document/d/1eDDIZCp_pD01cCeghum7fLRDqmEl3dfds9y3yI4W9Hw/edit Messaging system intake and release process]
 = Process: Shipping a New Mozilla Webextension =
@@ Line 429: / Line 470: @@
 == Extra information ==
+The steps for shipping a system add-on are described in detail here:
 [https://wiki.mozilla.org/Firefox/Go_Faster/System_Add-ons/Process https://wiki.mozilla.org/Firefox/Go_Faster/System_Add-ons/Process]
@@ Line 670: / Line 712: @@
 == Decisions ==
-* Timeline
+* Timeline (Refer to the [https://docs.google.com/document/d/1xiWjGqK-s3NiqEY-Qg34eAm1Nca5iqzEUE8udRX1ku0/edit feature rollout playbook] for help with this)
 * Products affected: Desktop, Fennec, ESR?
 * Platforms affected: All, Windows, Mac, Linux?
@@ Line 679: / Line 721: @@
 # File a bug for handling the rollout (examples: {{bug|1467514}} or {{bug|1523978}})
 # Development owner (likely mythmon) configures the recipe in Normandy to flip pref for targeted end-users
+# For release-unblockers/hotfixes, set up on stage, so QA can test on https://delivery-console.stage.mozaws.net
 # Release owner reviews, approves and publishes recipe
 # Feature team, release owner monitor data to verify: