Differences between revisions 17 and 19 (spanning 2 versions)
Revision 17 as of 2009-06-27 18:04:08
Size: 2015
Editor: LukClaes
Revision 19 as of 2010-09-18 17:15:36
Size: 2063
Editor: AdamBarratt
Comment: All point releases now are >= lenny, so drop the conditional
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from Teams/ReleaseManager/PointReleaseCheckList
Line 37: Line 38:
 * if version >= Lenny: Notify the DebianLive Team that the PointRelease is done  * Notify the DebianLive Team that the PointRelease is done

<!> 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.

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