Differences between revisions 48 and 61 (spanning 13 versions)
Revision 48 as of 2011-09-08 10:31:54
Size: 3457
Editor: PhilippKern
Comment: make debian-live "blue"
Revision 61 as of 2014-11-16 04:58:43
Size: 3968
Editor: PaulWise
Comment: one more autoupdated page
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 15: Line 16:
 * Coordinate date with the FTP-Team, [[Teams/DebianCd|Debian CD]] and PressTeam  * Coordinate date with the FTP-Team, [[Teams/DebianCd|Debian CD]] and [[Teams/Press|Press Team]]
Line 18: Line 19:
 * Ping for an updated ia32-libs
 * Make sure user-mode-linux is built against the latest kernel.
Line 19: Line 22:
 * Send an announcement of the date to debian-release, [[Teams/Security|Security Team]], PressTeam, [[Teams/DebianCd|Debian CD]], [[mailto:debian-live@lists.debian.org|debian-live]], debian-security@lists.debian.org, debian-kernel, debian-boot, debian-www  * 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
Line 21: Line 25:
 * Prepare PressAnnouncement  * Prepare [[Teams/Publicity/Announcements|Press Announcement]]
Line 29: Line 33:
== During the PointRelease == == During the Point Release ==

 * Deactivate the queue-viewer
Line 41: Line 47:
== After the PointRelease == == After the Point Release ==
Line 44: Line 50:
 * 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 [[Teams/DebianCd|Debian CD]] 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
 * N
otify 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
Line 51: Line 58:
 * Submit a new release to the [[http://freshmeat.net/projects/debian|Debian freshmeat page]]
Line 53: Line 59:
 * 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

  • 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)