Confirmed users
2,816
edits
Release Management/Release Process Checklist Documentation: Difference between revisions
Release Management/Release Process Checklist Documentation (view source)
Revision as of 19:54, 6 January 2020
, 6 January 2020→Nightly Checklist: added example bug
m (→Nightly Checklist: added link to updating status/tracking flags) |
m (→Nightly Checklist: added example bug) |
||
| Line 9: | Line 9: | ||
* '''Verify that the [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ release calendar] is up to date.''' This can be done in conjunction with the milestones document or after it’s published. | * '''Verify that the [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ release calendar] is up to date.''' This can be done in conjunction with the milestones document or after it’s published. | ||
* '''Ensure that the release has a [https://wiki.mozilla.org/Platform#Regression_Engineering_Owner_.28REO.29 Regression Engineering Owner] identified.''' Ultimately, ownership of this task falls within the Firefox engineering org. However, it is good for the release manager to ensure that this doesn’t get stalled. | * '''Ensure that the release has a [https://wiki.mozilla.org/Platform#Regression_Engineering_Owner_.28REO.29 Regression Engineering Owner] identified.''' Ultimately, ownership of this task falls within the Firefox engineering org. However, it is good for the release manager to ensure that this doesn’t get stalled. | ||
* On Merge Day: [[BMO/new-version|Add tracking and status flags]] for the new Nightly version. | * On Merge Day: [[BMO/new-version|Add tracking and status flags]] for the new Nightly version. Example bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1606669 | ||
On a daily (or thereabouts) basis, the following items should be monitored: | On a daily (or thereabouts) basis, the following items should be monitored: | ||