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 20:07, 12 August 2019

No change in size ,  12 August 2019
m
Updating to reflect that milestones document is now a tab in release tracking spreadsheet
m (→‎Launch Day: Updating sec adv push ownership)
m (Updating to reflect that milestones document is now a tab in release tracking spreadsheet)
Line 6: Line 6:


Prior to the start of the cycle, the follow tasks need to be performed:
Prior to the start of the cycle, the follow tasks need to be performed:
* '''Create a milestones document.''' This will ideally be ready at least two weeks prior to the start of the cycle, with feedback received from key stakeholders (QA, RelEng, RelMan) prior to wider publishing. There is not currently a template for this document because it’s still evolving from release to release, so it is advised to use the document from the previous release as a starting point.  
* '''Update the milestones tab on release tracking spreadsheet.''' [https://docs.google.com/spreadsheets/d/1Kexb-hd8chGEN63zZKqkBSxREe7nR_A2Ai2OuehaBaM/edit#gid=1793473785 Check milestones tab] of release template for how to. This will ideally be ready at least two weeks prior to the start of the cycle, with feedback received from key stakeholders (QA, RelEng, RelMan) prior to wider publishing.  
* '''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.
Line 58: Line 58:
* '''QA manual testing signoff for Desktop/DevEdition.''' Ask in the #qa-coordination Slack channel if there are questions about progress.
* '''QA manual testing signoff for Desktop/DevEdition.''' Ask in the #qa-coordination Slack channel if there are questions about progress.
* '''Update test on beta-cdntest.''' Once QA has performed update testing on the cdntest update channel, the builds are ready to ship.
* '''Update test on beta-cdntest.''' Once QA has performed update testing on the cdntest update channel, the builds are ready to ship.
* '''Push Desktop/DevEdition to Beta.''' The release is scheduled in ship-it by pushing the '''ship''' button for each release.
mil* '''Push Desktop/DevEdition to Beta.''' The release is scheduled in ship-it by pushing the '''ship''' button for each release.
[[Image:RelMan Process Ship-It v2 5.png|600px|center|middle]]
[[Image:RelMan Process Ship-It v2 5.png|600px|center|middle]]


Ritu Kothari
Confirmed users
229

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1216386"

Navigation menu