Differences between revisions 34 and 63 (spanning 29 versions)
Revision 34 as of 2011-02-02 21:38:05
Size: 2638
Editor: AdamBarratt
Comment: Larger notify list
Revision 63 as of 2021-03-24 01:42:28
Size: 4264
Editor: PaulWise
Comment: mention the need for CD testers to have a date in advance
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
== Before a PointRelease == == Before a Point Release ==
Line 11: Line 12:
 * Check with KernelTeam for specials with the Kernel  * Check with [[Teams/DebianKernel|Kernel Team]] for specials with the Kernel
Line 14: Line 15:
 * Coordinate date with the FTP-Team, Debian-CD and PressTeam  * 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 [[Teams/Press|Press Team]]
Line 16: Line 18:
 * Make sure base-files has been uploaded to update /etc/debian-version
 * Send an announcement of the date to debian-release, SecurityTeam, PressTeam, Debian-CD, debian-live, debian-security@ldo
 * Prepare PressAnnouncement
   * Have an item added to the [[Teams/DebianCD/ReleaseTesting|Debian CD release testing page]] so CD testers can make themselves available on the date
 * 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)
 * Ping for an updated ia32-libs
 * Make sure user-mode-linux is built against the latest kernel.
 * 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).
 * Prepare [[Teams/Publicity/Announcements|Press Announcement]]
Line 22: Line 30:
   * http://release.debian.org/stable/missing-security.html
Line 25: Line 34:
== During the PointRelease == == During the Point Release ==

 * Deactivate the queue-viewer
Line 28: Line 39:
   * List of packages (including bugnumbers) that needs to be removed (best: dak rm lines as prepared above)
     * /srv/ftp-master.debian.org/queue/$queue/COMMENTS/REMOVALS
   * 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
Line 33: Line 45:
 * Check if /org/ftp.debian.org/ftp/README was updated.  * Check if /srv/ftp-master.debian.org/ftp/README was updated.
Line 36: Line 48:
== After the PointRelease == == After the Point Release ==
Line 39: Line 51:
 * 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 DebianCD Team that the PointRelease is done
 * Notify the DebianLive Team that the PointRelease is done
 * Archive/tidy the COMMENTS directory and reactivate the queue-viewer
 * Notify debian-
security@lists.debian.org as people tend to cry occasionally
 * Notify the [[Teams/Press|PressTeam]], that Point Release is done (tell them when the Point Release will be pushed out)
 * Notify the [[Teams/DebianCd|Debian CD]] Team that the Point Release is done
 * Notify the DebianLive Team that the Point Release is done
 * Notify rha for Debian WSL build to update the filesystem tarball, sign and upload to Microsoft for onward distribution via Microsoft Store
Line 46: Line 60:
 * Submit a new release to the [[http://freshmeat.net/projects/debian|Debian freshmeat page]]
 * Propose a tweet/dent on the #debian-publicity IRC channel
 * Propose a tweet/dent on the [[irc://irc.debian.org/debian-publicity|#debian-publicity]] [[IRC]] channel
 * Submit a patch for the [[http://timeline.debian.net|Debian timeline]]
 * Update the version number on various wiki pages (DebianSqueeze DebianWheezy)

<!> 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 Point Release

During the Point Release

  • Deactivate the queue-viewer
  • 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 Point Release

  • Check that everything that should be released really was released
  • Archive/tidy the COMMENTS directory and reactivate the queue-viewer
  • Notify debian-security@lists.debian.org as people tend to cry occasionally

  • Notify the PressTeam, that Point Release is done (tell them when the Point Release will be pushed out)

  • Notify the Debian CD Team that the Point Release is done

  • Notify the DebianLive Team that the Point Release is done

  • Notify rha for Debian WSL build to update the filesystem tarball, sign and upload to Microsoft for onward distribution via Microsoft Store
  • Update the website
  • Watch mailing-lists for abnormalities
  • Notify Distrowatch; send a mail to distro@distrowatch.com

  • Propose a tweet/dent on the #debian-publicity IRC channel

  • Submit a patch for the Debian timeline

  • Update the version number on various wiki pages (DebianSqueeze DebianWheezy)