Differences between revisions 2 and 13 (spanning 11 versions)
Revision 2 as of 2008-01-17 10:27:16
Size: 1131
Editor: zobel
Comment:
Revision 13 as of 2009-02-07 22:51:37
Size: 2007
Editor: LukClaes
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
<!> 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 7:
 * Move packages from p-u-new to p-u  * Move remaining (suitable) packages from p-u-new to p-u
Line 9: Line 9:
 * Make sure removal bugs are assigned to release.d.o in the BTS and prepare dak rm lines for ftp-master.
Line 10: 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)
Line 17: Line 18:
   * 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 20: Line 25:
   * 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 23: Line 30:
 * Check if /org/ftp.debian.org/ftp/README was updated.
 * Check if dak.conf was updated to list the next webpage for p-u rejects.
Line 25: Line 34:
 * Check that everything that should be released really was released
Line 27: Line 37:
 * 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.
  • Make sure removal bugs are assigned to release.d.o in the BTS and prepare dak rm lines for ftp-master.
  • 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 ?PressTeam 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.
  • Check if dak.conf was updated to list the next webpage for p-u rejects.

After the PointRelease

  • Check that everything that should be released really was released
  • 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