Confirmed users
229
edits
Release Management/Release Process Checklist Documentation: Difference between revisions
Release Management/Release Process Checklist Documentation (view source)
Revision as of 18:23, 12 August 2019
, 12 August 2019→Launch Day: Updating sec adv push ownership
m (→Post-Launch: added walk through for samsung upload) |
Ritu Kothari (talk | contribs) m (→Launch Day: Updating sec adv push ownership) |
||
| Line 144: | Line 144: | ||
* '''Verify that the release notes are live.''' | * '''Verify that the release notes are live.''' | ||
* '''Verify versions in firefox_versions.json and mobile_versions.json.''' This can probably be moved into a step where we verify a number of things on the delivery dashboard. | * '''Verify versions in firefox_versions.json and mobile_versions.json.''' This can probably be moved into a step where we verify a number of things on the delivery dashboard. | ||
* '''Security advisories go live.''' This | * '''Security advisories go live.''' Starting with 69 launch, release owner (from relman team) will own pushing the sec advisory live. This used to be handled by the security team post-launch. | ||
* Email announce list. Send an email confirming the new release, following the general form shown on the [https://wiki.mozilla.org/Release_Management/Release_Days#Release_day_2 release wiki page]. | * Email announce list. Send an email confirming the new release, following the general form shown on the [https://wiki.mozilla.org/Release_Management/Release_Days#Release_day_2 release wiki page]. | ||
* '''Schedule Desktop update rate to 0% in Balrog after 24 hours.''' It is recommended to do this on launch day to avoid forgetting about it the day after. This change can be made in Balrog by either RelEng or RelMan, though both will need to sign off on the rule change afterwards. | * '''Schedule Desktop update rate to 0% in Balrog after 24 hours.''' It is recommended to do this on launch day to avoid forgetting about it the day after. This change can be made in Balrog by either RelEng or RelMan, though both will need to sign off on the rule change afterwards. | ||