Differences between revisions 1 and 62 (spanning 61 versions)
Revision 1 as of 2008-01-17 10:25:58
Size: 1041
Editor: zobel
Comment:
Revision 62 as of 2020-07-20 09:41:14
Size: 4111
Editor: ?AndyCater
Comment: Adding Debian WSL into the picture
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 5: Line 7:
== Before a PointRelease ==
 * Move packages from p-u-new to p-u
 * Send the preparation mail.
 * Check with KernelTeam for specials with the Kernel
 * Check with d-i team for specials with this update
 * 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
== Before a Point Release ==
Line 17: Line 9:
== While the PointRelease ==  * Move remaining (suitable) packages from p-u-new to p-u
 * Make sure removal bugs are assigned to release.d.o in the BTS and mentioned in the queue-viewer
   * /org/{o-,}p-u-new/COMMENTS/REMOVALS
 * Check with [[Teams/DebianKernel|Kernel Team]] 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
 * 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]]
   * Have an FTP-master ready/notified/available 3 weeks before the Point Release
 * 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]]
   * coordinate with d-i team for text for d-i changes
   * Generate the mail using point-release-mail.
 * Review that security archive is in sync with stable + p-u
   * http://release.debian.org/stable/missing-security.html
 * Review that p-u is built on all arches for all packages
 * Prepare the website changes

== During the Point Release ==

 * Deactivate the queue-viewer
Line 19: Line 37:
   * Need the d-i to be moved from p-u?    * 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?
Line 21: Line 43:
 * Check /srv/ftp-master.debian.org/ftp/dists/$codename/ChangeLog
 * Check if /srv/ftp-master.debian.org/ftp/README was updated.
Line 23: Line 47:
== After the PointRelease ==
 * 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
 * Watch ML for abnormalies
== 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 [[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
 * Update the website
 * Watch mailing-lists for abnormalities
 * Notify Distrowatch; send a mail to distro@distrowatch.com
 * 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)