Release Management/Release Process Checklist Documentation: Difference between revisions

Release Management/Release Process Checklist Documentation (view source)

Revision as of 17:18, 2 August 2023

515 bytes added , 2 August 2023

no edit summary

Dmeehan

383

edits

@@ Line 509: / Line 509: @@
 # Update PI request if there have been any changes since the last QA signoff.
-==As available, the following should be monitored/performed during RC week==
+==As available, the following should be monitored/performed during RC week for Desktop/Android==
 # Phabricator patches for remote-settings updates are generated automatically. Typically this is every Monday and Thursday. These patches must be included in release/esr uplifts.
 #* Monitor email notifications sent by Phabricator: “No Bug, mozilla-release repo-update HSTS HPKP remote-settings tld-suffixes”/“No Bug, mozilla-esr91 repo-update HSTS HPKP remote-settings tld-suffixes”
@@ Line 524: / Line 524: @@
 # Verify that QA have signed off update tests on Beta
 #* QA will post a message to the [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] Slack channel when they complete update testing and another message when they complete functional testing.
-#* Build validation testing is tracked [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=162277457 here]
 # Verify that QA have signed off update tests on release-localtest
 #* QA will post a message to the [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] Slack channel when they complete update testing and another message when they complete functional testing.
-#* Build validation testing is tracked [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=162277457 here]
+# Monitor for QA sign-off on Fenix/Focus build validation before proceeding with Steps 7 to 12.
-# Monitor for QA sign-off on Fenix/Focus build validation before proceeding with Steps 4 to 9.
 #* Please Note: Build Validation sign-off is usually provided the day after Fenix/Focus builds are produced.
-#* Focus and Fenix QA sign-off are sent via [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] Slack Channel, with wording such as:
+#* Focus and Fenix QA sign-off are sent via [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] Slack Channel.
-#** [Mobile] Firefox RC xxx.x.x - Manual testing sign-off[GREEN]
-#** [Mobile] Focus RC xxx.x.x - Manual and automated testing sign-off [Green]
 # Ship Fenix from ship-it via Ship
 # Roll out Fenix to the Production track at 5% in google play
@@ Line 550: / Line 546: @@
 # Upload [https://seller.samsungapps.com/application/main.as?contentId=000003397900&platform=&readOnly=Y#/cert/info Focus to Samsung Store] with 5% rollout when approved
 #* Perform the same steps as Step 8
+==As available, the following should be monitored/performed during RC week for iOS==
+# Monitor for QA sign-off on Firefox/Focus iOS build validation before proceeding with Steps 2 to 6.
+#* Please Note: Build Validation sign-off is usually provided the day after the builds are produced.
+#* Firefox iOS and Focus iOS QA sign-off are sent via [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] Slack Channel.
+# Submit iOS Focus in the AppStore for review.
+#* Select a phased rollout when submitting
+# Submit iOS Klar in the AppStore for review.
+#* Select a phased rollout when submitting
+# Add the External Beta Testers group to the Firefox Beta TestFlight Build
+# Gather Firefox iOS release notes.
+#* This can be done in parallel to the Desktop/Android release note gathering.
+#* The store release notes are needed before submitting.
+# Submit Firefox iOS in the AppStore for review.
+#* Select a phased rollout when submitting.
 =RC Uplifts=
@@ Line 583: / Line 594: @@
 ==The following tasks need to be performed prior to go-live==
-# Ensure that feedback for release notes was gathered by UX/Product
+# Ensure that feedback for release notes was gathered.
 #* Monitor the [https://mozilla.slack.com/archives/C9L102H6X #release-notes] Slack channel
-#* For more information on the UX/Product release notes doc process see [https://docs.google.com/document/d/1rO4fdlYzQ8M2QfJVtE9P803V1GSvBypVC_G8RVIcmTQ/edit here]
+#* For more information on the release notes doc process see [https://wiki.mozilla.org/Release_Management/Release_Notes here]
 # Incorporate feedback into draft release notes.
 #* Add a release in Nucleus for [https://nucleus.mozilla.org/admin/rna/release/1013/change/ Firefox], [https://nucleus.mozilla.org/admin/rna/release/1012/change/ Firefox for Android], [https://nucleus.mozilla.org/admin/rna/release/1011/change/ Firefox for iOS]