Changes

Jump to: navigation, search

Release Management/ESR Release Checklist Documentation

826 bytes added, 13:59, 16 August 2023
Adding steps for extended support cli steps
== Launch Day ==
* '''Schedule push to esr at 100% (ship-it).''' Go-Live time is usually 6am PT on launch day, but this can be done ahead of time with a scheduled rule change in Balrog. Unlike non-ESR Firefox releases, ESR releases go out at 100% from day 1 rather than a staged rollout.
* '''Release Ubuntu's snap to the main ESR population.''' This can be done by going to https://snapcraft.io/firefox/releases and dragging the candidate version onto the stable channel on the corresponding ESR track. In the case that there are two ESR versions during the extended support period (for example 102 and 115), Canonical would need to create a new branch for the oldest version. The builds will be updated on the new branch by Canonical. When ready to ship, you must use Snapcraft CLI to release this version. Using the example of ESR102 and ESR115, ESR115 would be released to the stable channel on the esr track using the WebUI. After confirming that all builds are built on the custom branch, you would run the following command  snapcraft promote --from-channel=esr/candidate/102 --to-channel=esr/stable/102 firefox : If for any reason this '''cannot''' be done on the WebUI, here are some manual steps. Supposing you have docker installed on your machine, run the following commands:
docker run -ti snapcore/snapcraft:stable
snapcraft release firefox $SNAP_REVISION esr/stable
snapcraft close firefox esr/candidate
: $SNAP_REVISION is a number (ex: 370) that can be found at https://dashboard.snapcraft.io/snaps/firefox/, it is not the esr release number. Closing "esr/candidate" will move the users to the "esr/stable" channel. They will get back to "esr/candidate" the day we reopen it.
* '''Make release notes live.''' There is a 15-20min lag between making the change in Nucleus and the live website picking up this change, so plan to do this 15-30min prior to go-live.
* '''Signoff on scheduled rule change in Balrog.''' Assuming that the change is scheduled for 6am PT, this can be signed off ASAP to avoid unnecessary delays at go-live time.
193
edits

Navigation menu