1041
Comment:
|
2194
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
<!> This is a SRM's TODO list, which might not be authorativ or complete. | ## page was renamed from Teams/ReleaseManager/PointReleaseCheckList ## page was renamed from Teams/ReleaseManager/Teams/ReleaseManager/PointReleaseCheckList <!> This is a SRM's TODO list, which might not be authorative or complete. |
Line 6: | Line 8: |
* Move packages from p-u-new to p-u | * Move remaining (suitable) packages from p-u-new to p-u |
Line 8: | Line 10: |
* Generate the mail using point-release-mail. * Send a mail to the Press team * Make sure removal bugs are assigned to release.d.o in the BTS and prepare dak rm lines for ftp-master. * They are mentioned in the queue-viewer |
|
Line 9: | Line 15: |
* Check with d-i team for specials with this update | * 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) |
Line 16: | Line 22: |
* coordinate with d-i team for text for d-i changes * 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 |
|
Line 19: | Line 29: |
* Need the d-i to be moved from p-u? | * List of packages that needs to be released * List of packages (including bugnumbers) that needs to be removed (best: dak rm lines as prepared above) * Need d-i to be moved from p-u? |
Line 22: | Line 34: |
* Check if /org/ftp.debian.org/ftp/README was updated. | |
Line 24: | Line 37: |
* Check that everything that should be released really was released * Notify debian-security as people tend to cry occassionally |
|
Line 26: | Line 41: |
* Watch ML for abnormalies | * Notify the DebianLive Team that the PointRelease is done * Update the website * Watch ML for abnormalities |
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
- Send the preparation mail.
- Generate the mail using point-release-mail.
- Send a mail to the Press team
- Make sure removal bugs are assigned to release.d.o in the BTS and prepare dak rm lines for ftp-master.
- They are mentioned in the queue-viewer
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
- Coordinate date with the FTP-Team
Notify the SecurityTeam of an upcoming ?PointRelease
Notify the Debian-CD team of an upcoming ?PointRelease
Prepare ?PressAnnouncement
- coordinate with d-i team for text for d-i changes
- 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
While the PointRelease
- Check with the FTP-Masters
- List of packages that needs to be released
- List of packages (including bugnumbers) that needs to be removed (best: dak rm lines as prepared above)
- Need d-i to be moved from p-u?
- Need to decruft?
- Sign the release file
- Check if /org/ftp.debian.org/ftp/README was updated.
After the PointRelease
- Check that everything that should be released really was released
- Notify debian-security as people tend to cry occassionally
Notify the ?PressTeam, that ?PointRelease is done (tell them when the ?PointRelease will be pushed out)
Notify the DebianCD Team that the ?PointRelease is done
Notify the DebianLive Team that the ?PointRelease is done
- Update the website
- Watch ML for abnormalities