1617
Comment: +check README
|
1731
note about d-i purged
|
Deletions are marked like this. | Additions are marked like this. |
Line 7: | Line 7: |
* Move packages from p-u-new to p-u | * Move remaining (suitable) packages from p-u-new to p-u |
Line 11: | Line 11: |
* 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) |
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.
- Make sure removal bugs are assigned to ftp.d.o in the BTS
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
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
- 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.