273
edits
Release Management/Release Process Checklist Documentation: Difference between revisions
Jump to navigation
Jump to search
Release Management/Release Process Checklist Documentation (view source)
Revision as of 16:22, 13 January 2023
, 13 January 2023Updated android steps for RC checklist
No edit summary |
(Updated android steps for RC checklist) |
||
| Line 425: | Line 425: | ||
==The following tasks need to be performed at the start of RC week (week before go-live)== | ==The following tasks need to be performed at the start of RC week (week before go-live)== | ||
# Sync with RelEng to merge Beta to Release. | # Review tracking-firefoxXXX+ bugs and approval requests | ||
#* Send an email with details of the merge. | #* Verify that all approved uplift requests were uplifted to beta | ||
#* Include both [https://groups.google.com/a/mozilla.org/g/release-drivers release-drivers] and [https://groups.google.com/a/mozilla.org/g/release-signoff release sign-off] | # Verify all approved bugs landed on mozilla-release | ||
#* [https://groups.google.com/a/mozilla.org/g/release-drivers/c/kCYe68Gglng Example email] | #* Sync with RelEng to merge Beta to Release. | ||
# Once the merge is complete, | #** Send an email with details of the merge. | ||
#** Include both [https://groups.google.com/a/mozilla.org/g/release-drivers release-drivers] and [https://groups.google.com/a/mozilla.org/g/release-signoff release sign-off] | |||
#** [https://groups.google.com/a/mozilla.org/g/release-drivers/c/kCYe68Gglng Example email] | |||
# Once the merge is complete, verify that the [https://treeherder.mozilla.org/jobs?repo=mozilla-release Treeherder] tests green/starred | |||
# Set up Desktop build in [https://shipit.mozilla-releng.net/ Ship-It]. | |||
## Connect to the VPN. | ## Connect to the VPN. | ||
## Log into [https://shipit.mozilla-releng.net/ Ship-It]. | ## Log into [https://shipit.mozilla-releng.net/ Ship-It]. | ||
| Line 439: | Line 443: | ||
## Click Submit. | ## Click Submit. | ||
##* [[File:Screen Shot 2022-06-07 at 9.27.24 AM.png|thumb|center]] | ##* [[File:Screen Shot 2022-06-07 at 9.27.24 AM.png|thumb|center]] | ||
# Start build from [https://shipit.mozilla-releng.net/ Ship-It] via Promote RC. | # Start the Desktop build from [https://shipit.mozilla-releng.net/ Ship-It] via Promote RC. | ||
#* [[File:Screenshot 2022-06-07 at 09-28-44 RelMan Activities Overview.png|thumb|center]] | #* [[File:Screenshot 2022-06-07 at 09-28-44 RelMan Activities Overview.png|thumb|center]] | ||
#* Click the Schedule button. | #* Click the Schedule button. | ||
#** [[File:Screenshot 2022-06-07 at 09-31-56 RelMan Activities Overview.png|thumb|center]] | #** [[File:Screenshot 2022-06-07 at 09-31-56 RelMan Activities Overview.png|thumb|center]] | ||
# Confirm | # Confirm Desktop build has started. | ||
#* Taskcluster email: “[desktop] Build of firefox xx.0 build 1” | #* Taskcluster email: “[desktop] Build of firefox xx.0 build 1” | ||
# Bump | # Bump Firefox Android version number from XXX.0bX to X.1.0 | ||
#* See [https://github.com/mozilla-mobile/ | #* See [https://github.com/mozilla-mobile/firefox-android/commit/0d78c43f16fda39b5ac39b9ac5eea1d8a1e793a9 Example] | ||
# Bump | # Bump Fenix version number from XXX.0bX to X.1.0 | ||
#* See [https://github.com/mozilla-mobile/ | #* See [https://github.com/mozilla-mobile/fenix/commit/ce4df9b8a71df7ab6e9b873910df1308fd183c96 Example] | ||
# | # Create Firefox Android GV bump PR and change track if necessary. | ||
## Fork the release branch. | ## Fork the release branch. | ||
## Change and commit the following: | ## Change and commit the following: | ||
##* | ##* android-components/plugins/dependencies/src/main/java/Gecko.kt | ||
##** Change the GeckoView Version to the RC1 GeckoView package | ##** Change the GeckoView Version to the RC1 GeckoView package. | ||
##*** Please Note: The package number for RC1 can be found in [https://maven.mozilla.org/?prefix=maven2/org/mozilla/geckoview/geckoview/ Maven] | ##*** Please Note: The package number for RC1 can be found in [https://maven.mozilla.org/?prefix=maven2/org/mozilla/geckoview/geckoview/ Maven] | ||
##** Change the GeckoChannel from beta to release | ##** Change the GeckoChannel from beta to release. | ||
##*** From ''val channel = GeckoChannel.BETA'' to ''val channel = GeckoChannel.RELEASE'' | ##*** From ''val channel = GeckoChannel.BETA'' to ''val channel = GeckoChannel.RELEASE'' | ||
## Create a PR to merge the fork into the release branch and request review from another release management team member. | ## Create a PR to merge the fork into the release branch and request review from another release management team member. | ||
##* See [https://github.com/mozilla-mobile/android | ##* See [https://github.com/mozilla-mobile/firefox-android/pull/518 Example] | ||
## Once the PR is approved and the CI tests pass, merge the PR. | ## Once the PR is approved and the CI tests pass, merge the PR. | ||
# Check if there are any pending PRs for | # Check if there are any pending PRs for firefox-android/fenix release branch before proceeding with the steps to build Fenix/Focus. | ||
#* [https://github.com/mozilla-mobile/firefox-android/pulls firefox-android] | |||
#* [https://github.com/mozilla-mobile/fenix/pulls fenix] | #* [https://github.com/mozilla-mobile/fenix/pulls fenix] | ||
#* Example Filter: ''is:pr is:open base: releases_v101.0'' | #* Example Filter: ''is:pr is:open base: releases_v101.0'' | ||
#* If the pending PR is reviewed and is waiting on CI, then where possible wait until the PR has been merged. | #* If the pending PR is reviewed and is waiting on CI, then where possible wait until the PR has been merged. | ||
#* If ever unsure, reach out on the | #* If ever unsure, reach out on the android team Slack channel [https://mozilla.slack.com/archives/C016PEDKY90 #mobile-android-team] | ||
# | # Set up Firefox Android (AC, Focus) release in Ship-It. | ||
# | #* Follow the same steps as creating a beta build. | ||
# | # Start Firefox Android (AC, Focus) release in Ship-It via Promote. | ||
# | # Confirm notification sent when Firefox Android builds finish. | ||
# Push AC/Focus release in Ship-It via Push. | |||
# Confirm that AC bump PR has landed in Fenix repo. | |||
# Set up Fenix build in Ship-It. | # Set up Fenix build in Ship-It. | ||
#* Follow the same steps as creating a beta build. | #* Follow the same steps as creating a beta build. | ||
# Start Fenix build from Ship-It via Promote. | # Start Fenix build from Ship-It via Promote. | ||
# Confirm notification sent when Desktop builds finish. | |||
# Confirm | |||
#* Taskcluser email: “firefox xxx.0 build1/mozilla-release is in the candidates directory” | #* Taskcluser email: “firefox xxx.0 build1/mozilla-release is in the candidates directory” | ||
# Push Desktop to Beta at 100% from Ship-It via Ship RC | # Push Desktop to Beta at 100% from Ship-It via Ship RC. | ||
#* [[File:Screenshot 2022-06-07 at 09-32-46 RelMan Activities Overview.png|thumb|center]] | #* [[File:Screenshot 2022-06-07 at 09-32-46 RelMan Activities Overview.png|thumb|center]] | ||
#* Click the Schedule button. | #* Click the Schedule button. | ||
#** [[File:Screenshot 2022-06-07 at 10-28-30 RelMan Activities Overview.png|thumb|center]] | #** [[File:Screenshot 2022-06-07 at 10-28-30 RelMan Activities Overview.png|thumb|center]] | ||
# Verify that the Balrog rule changes are live | # Verify that the Balrog rule changes are live. | ||
## View the [https://balrog.services.mozilla.com/rules?product=Firefox&channel=beta Balrog Rules for Firefox Beta]. | ## View the [https://balrog.services.mozilla.com/rules?product=Firefox&channel=beta Balrog Rules for Firefox Beta]. | ||
## Verify that the Background Rate for Firefox-xx.0-build1 is 100. | ## Verify that the Background Rate for Firefox-xx.0-build1 is 100. | ||
| Line 513: | Line 516: | ||
#* Update the Release Milestones (Details) section to add Status (On Track, Delayed), Ship Date. | #* Update the Release Milestones (Details) section to add Status (On Track, Delayed), Ship Date. | ||
#* Review the Release Milestones section dates and update the status. | #* Review the Release Milestones section dates and update the status. | ||
# Verify that QA have signed off manual testing for Desktop | |||
#* 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 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 4 to 9. | # 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. | #* Please Note: Build Validation sign-off is usually provided the day after Fenix/Focus builds are produced. | ||
| Line 535: | Line 547: | ||
# Upload [https://seller.samsungapps.com/application/main.as?contentId=000003397900&platform=&readOnly=Y#/cert/info Focus to Samsung Store] with 5% rollout when approved | # 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 | #* Perform the same steps as Step 8 | ||
=RC Uplifts= | =RC Uplifts= | ||