Differences between revisions 33 and 35 (spanning 2 versions)
Revision 33 as of 2011-02-02 21:36:31
Size: 2569
Editor: AdamBarratt
Comment: Merge preparation mail and press mail steps
Revision 35 as of 2011-02-02 21:39:22
Size: 2645
Editor: AdamBarratt
Comment: /ftp/ is in /srv/ftp*-master*.d.o these days
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
 * Notify the SecurityTeam of an upcoming PointRelease  * Send an announcement of the date to debian-release, SecurityTeam, PressTeam, Debian-CD, debian-live, debian-security@ldo
Line 33: Line 33:
 * Check if /org/ftp.debian.org/ftp/README was updated.  * Check if /srv/ftp-master.debian.org/ftp/README was updated.

<!> 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
  • 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 ?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, Debian-CD and ?PressTeam

    • 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
  • Send an announcement of the date to debian-release, SecurityTeam, ?PressTeam, Debian-CD, debian-live, debian-security@ldo

  • Prepare ?PressAnnouncement

    • 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
  • Review that p-u is built on all arches for all packages
  • Prepare the website changes

During 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)
      • /srv/ftp-master.debian.org/queue/$queue/COMMENTS/REMOVALS
    • 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 PointRelease

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

  • Update the website
  • Watch mailing-lists for abnormalities
  • Notify Distrowatch; send a mail to distro@distrowatch.com

  • Submit a new release to the Debian freshmeat page

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