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 15:20, 10 January 2023
, 10 January 2023Updated beta merge days steps to reflect firefox-android (AC/Focus)
(Updated nightly steps for Android) |
(Updated beta merge days steps to reflect firefox-android (AC/Focus)) |
||
| Line 219: | Line 219: | ||
#* Taskcluser email: “firefox xxx.0b1 build1/mozilla-beta has been pushed to cdntest” | #* Taskcluser email: “firefox xxx.0b1 build1/mozilla-beta has been pushed to cdntest” | ||
#* Taskcluser email: “devedition xxx.0b1 build1/mozilla-beta has been pushed to cdntest” | #* Taskcluser email: “devedition xxx.0b1 build1/mozilla-beta has been pushed to cdntest” | ||
# Perform the release management steps in the [https://mozac.org/contributing/release-checklist | # Perform the release management steps in the [https://mozac.org/contributing/release-checklist Release checklist] | ||
#* | #* The Firefox Android (Android-Components, Focus) release branch is used for beta and rc builds. This step can be performed before the Beta 1 build has shipped to the beta channel, geckoview is built during the promote phase. | ||
# Perform the release management steps in [https://github.com/mozilla-mobile/fenix/wiki/Creating-a-release-branch Fenix - Creating a release branch] | # Perform the release management steps in [https://github.com/mozilla-mobile/fenix/wiki/Creating-a-release-branch Fenix - Creating a release branch] | ||
#* This Fenix | #* This Fenix release branch is used for beta and rc builds. | ||
# Create Firefox Android (AC, Focus) release in Ship-It | |||
# Create AC release in Ship | |||
#* Once the PR to change the GeckoChannel and the PR to bump the geckoview have both merged, go to ship-it and create new release. | #* Once the PR to change the GeckoChannel and the PR to bump the geckoview have both merged, go to ship-it and create new release. | ||
# | # Start Firefox Android (AC, Focus) release in Ship-It via Promote | ||
#* | # Confirm notification sent when the Firefox Android (AC, Focus) builds finish | ||
# Set up a Fenix build in Ship-it | #* Taskcluster email: “Focus XXXb#-build1 is available at usual Taskcluster index" | ||
# Push AC/Focus release in Ship-It via Push | |||
# Confirm that AC bump PR has landed in Fenix repo | |||
# Set up a Fenix build in Ship-it | |||
#* Please note: you can only start a ship-it build on a revision that has a completed decision task | #* Please note: you can only start a ship-it build on a revision that has a completed decision task | ||
# Start a Fenix build from ship-it via Promote | # Start a Fenix build from ship-it via Promote | ||
# Confirm notification sent when the Fenix build finishes | |||
#* Taskcluster email: “fenix XXX.0b# build1 has been pushed to the closed testing track on Google Play" | |||
# Ship Fenix from ship-it via Ship | # Ship Fenix from ship-it via Ship | ||
# Monitor for QA sign-off on functional testing, before proceeding with Step 24. | # Monitor for QA sign-off on functional testing, before proceeding with Step 24. | ||
#* Please Note: Build Validation sign-off is usually provided the day after Merge Day. | #* Please Note: Build Validation sign-off is usually provided the day after Merge Day. | ||