Release Management/Worry Lists: Difference between revisions
(Created page with "Starting with the Firefox 14 release when Release Management became more than one person's job, a practice was developed called "worry list" which is a way to keep a record of...") |
|||
| Line 4: | Line 4: | ||
==Historical Worry Lists== | ==Historical Worry Lists== | ||
These examples demonstrate how worry lists have been used over the course of the last few years: | |||
* [https://etherpad.mozilla.org/firefox14-worry-list Firefox 14] | * [https://etherpad.mozilla.org/firefox14-worry-list Firefox 14] | ||
* [https://etherpad.mozilla.org/firefox15-worry-list Firefox 15] | * [https://etherpad.mozilla.org/firefox15-worry-list Firefox 15] | ||
* [https://etherpad.mozilla.org/firefox24-worry-list Firefox 24] | |||
* [https://etherpad.mozilla.org/firefox36-worry-list Firefox 36] | |||
Revision as of 00:52, 6 March 2015
Starting with the Firefox 14 release when Release Management became more than one person's job, a practice was developed called "worry list" which is a way to keep a record of what the release manager on point for a release is 'worrying' about. Truly it becomes a place to store the current status of certain bugs, track what bugs are needed on a particular Beta release, and keep general notes related to timing throughout the 18 weeks of a version number's time in the release management spectre.
There is a worry list template which helps identify some of the main areas of interest another release manager might have if they were to suddenly be handed a release in mid-stream.
Historical Worry Lists
These examples demonstrate how worry lists have been used over the course of the last few years: