|
Size: 1257
Comment:
|
Size: 3606
Comment: make the list of notications copy-pastable
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from Teams/ReleaseManager/PointReleaseCheckList | |
| Line 2: | Line 3: |
| <!> This is a SRM's TODO list, which might not be authorativ or complete. | <!> This is a SRM's TODO list, which might not be authorative or complete. |
| Line 7: | Line 8: |
| * Move packages from p-u-new to p-u * Send the preparation mail. |
* Move remaining (suitable) packages from p-u-new to p-u * Make sure removal bugs are assigned to release.d.o in the BTS and mentioned in the queue-viewer * /org/{o-,}p-u-new/COMMENTS/REMOVALS |
| Line 10: | Line 13: |
| * Check with d-i team for specials with this update * Check, if ReleaseNotes need to be updated. If yes, coordinate with translators * Coordinate date with the FTP-Team * Notify the SecurityTeam of an upcoming PointRelease * Notify the PressTeam of an upcoming PointRelease * Notify the Debian-CD team of an upcoming PointRelease |
* Check with d-i team for specials with this update (check esp. if old versions of d-i should be purged if new versions enter $suite's d-i area) * Check if ReleaseNotes need to be updated. If yes, coordinate with translators * Check if the [[Teams/Security|Security Team]]'s debtags need to be updated. If so, coordinate with EnricoZini. * Coordinate date with the FTP-Team, [[Teams/DebianCd|Debian CD]] and PressTeam * Have an FTP-master ready/notified/available 3 weeks before the Point Release * Make sure base-files has been uploaded to update /etc/debian-version (this can be lingering in p-u-NEW for a while in advance, too) * Check whether any packages need adding or updating in $suite-r0 * Send an announcement of the date to the release, security, press, CD, live, kernel, installer and web teams using this list of addresses: * debian-release@lists.debian.org, security@debian.org, press@debian.org, debian-cd@lists.debian.org, debian-live@lists.debian.org, debian-security@lists.debian.org, debian-kernel@lists.debian.org, debian-boot@lists.debian.org, debian-www@lists.debian.org * Send an announcement to debian-stable-announce encouraging people to test stuff in p-u (for the misc bugfixes, not the incorporated DSAs, see [[http://lists.debian.org/debian-stable-announce/2011/03/msg00002.html|SUA3-1]] for an example). |
| Line 18: | Line 25: |
| * Generate the mail using point-release-mail. * Review that security archive is in sync with stable + p-u * http://release.debian.org/stable/missing-security.html * Review that p-u is built on all arches for all packages * Prepare the website changes |
|
| Line 19: | Line 31: |
| == While the PointRelease == | == During the PointRelease == |
| Line 21: | Line 34: |
| * Need the d-i to be moved from p-u? | * List of packages that needs to be released * List of packages (including bug numbers) that need to be removed * /srv/ftp-master.debian.org/queue/$queue/COMMENTS/REMOVALS , displayed on queue-viewer * List of packages that need updating in $suite-r0 * Need d-i to be moved from p-u? |
| Line 23: | Line 40: |
| * Check /srv/ftp-master.debian.org/ftp/dists/$codename/ChangeLog * Check if /srv/ftp-master.debian.org/ftp/README was updated. |
|
| Line 26: | Line 45: |
| Line 27: | Line 47: |
| * Notify debian-security@lists.debian.org as people tend to cry occassionally | |
| Line 28: | Line 49: |
| * Notify the DebianCD Team that the PointRelease is done * Watch ML for abnormalies |
* Notify the [[Teams/DebianCd|Debian CD]] Team that the PointRelease is done * Notify the DebianLive Team that the PointRelease is done * Update the website * Watch mailing-lists for abnormalities * Notify Distrowatch; send a mail to distro@distrowatch.com * Submit a new release to the [[http://freshmeat.net/projects/debian|Debian freshmeat page]] * Propose a tweet/dent on the [[irc://irc.debian.org/debian-publicity|#debian-publicity]] [[IRC]] channel |
This is a SRM's TODO list, which might not be authorative or complete.
The following things need to be done for a point release:
Before a PointRelease
- Move remaining (suitable) packages from p-u-new to p-u
- Make sure removal bugs are assigned to release.d.o in the BTS and mentioned in the queue-viewer
- /org/{o-,}p-u-new/COMMENTS/REMOVALS
Check with ?KernelTeam for specials with the Kernel
- Check with d-i team for specials with this update (check esp. if old versions of d-i should be purged if new versions enter $suite's d-i area)
Check if ReleaseNotes need to be updated. If yes, coordinate with translators
Check if the Security Team's debtags need to be updated. If so, coordinate with EnricoZini.
Coordinate date with the FTP-Team, Debian CD and ?PressTeam
- Have an FTP-master ready/notified/available 3 weeks before the Point Release
- Make sure base-files has been uploaded to update /etc/debian-version (this can be lingering in p-u-NEW for a while in advance, too)
- Check whether any packages need adding or updating in $suite-r0
- Send an announcement of the date to the release, security, press, CD, live, kernel, installer and web teams using this list of addresses:
Send an announcement to debian-stable-announce encouraging people to test stuff in p-u (for the misc bugfixes, not the incorporated DSAs, see SUA3-1 for an example).
Prepare ?PressAnnouncement
- coordinate with d-i team for text for d-i changes
- Generate the mail using point-release-mail.
- Review that security archive is in sync with stable + p-u
- Review that p-u is built on all arches for all packages
- Prepare the website changes
During the PointRelease
- Check with the FTP-Masters
- List of packages that needs to be released
- List of packages (including bug numbers) that need to be removed
- /srv/ftp-master.debian.org/queue/$queue/COMMENTS/REMOVALS , displayed on queue-viewer
- List of packages that need updating in $suite-r0
- Need d-i to be moved from p-u?
- Need to decruft?
- Check /srv/ftp-master.debian.org/ftp/dists/$codename/ChangeLog
- Check if /srv/ftp-master.debian.org/ftp/README was updated.
- Sign the release file
After the PointRelease
- Check that everything that should be released really was released
Notify debian-security@lists.debian.org as people tend to cry occassionally
Notify the ?PressTeam, that ?PointRelease is done (tell them when the ?PointRelease will be pushed out)
Notify the DebianLive Team that the ?PointRelease is done
- Update the website
- Watch mailing-lists for abnormalities
Notify Distrowatch; send a mail to distro@distrowatch.com
Submit a new release to the Debian freshmeat page
Propose a tweet/dent on the #debian-publicity IRC channel