ReleaseChecklist
Differences between revisions 4 and 5
|
Size: 1116
Comment: add about-ubuntu check
|
Size: 722
Comment: breakdown and expand
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
== Before building candidates == |
|
| Line 13: | Line 15: |
| * prepare release announcement | |
| Line 14: | Line 17: |
| == Release timeline: == | == Once final image is ready == |
| Line 16: | Line 19: |
| * 7 days prior: | * push isos to mirror pool and verify |
| Line 18: | Line 21: |
| * release candidate release | == Before public release == |
| Line 20: | Line 23: |
| * '''FINAL ARTWORK''' * draft release announcement * 1 day before: * finalise release announcement * get release announcement translated * finalise media announcement list (list of email addresses, and who is sending) * make sure candidate final iso is in pool dir on mirror-master * verify torrents are working * verify that all servers have the image internally (releases, archive, cdimage) * on publishing: * check that http://releases.ubuntu.com/ has the proper links and text * check final torrents |
* push links to mirrors and verify * check torrent functionality |
These are things that needed to be checked for any release (preview, release candidate, and final) by the release manager:
Before building candidates
- change the description in dists/xxx/Release
- check the volume labels on ISO's for all architectures (cdimage/debian-cd/CONF.sh, OFFICIAL variable)
- check the lsb-release output for accuracy
- check /etc/issue and /etc/issue.net for accuracy
- ensure that the "about ubuntu" documents refer to the correct version, if at all
- prepare release announcement
Once final image is ready
- push isos to mirror pool and verify
Before public release
- push links to mirrors and verify
- check torrent functionality
ReleaseChecklist (last edited 2020-04-17 08:29:10 by sil2100)