todo foo

[dak.git] / docs / README.stable-point-release

diff --git a/docs/README.stable-point-release b/docs/README.stable-point-release
index 5adfbe2a02546a8d685186445364850628063151..176b33eb89d9c2aa3317ed9ad71639b7a847b4f7 100644 (file)
--- a/docs/README.stable-point-release
+++ b/docs/README.stable-point-release
@@ -4,6 +4,8 @@ Rough Guide to doing Stable Point Releases in Debian
 o run 'dak clean-proposed-updates' to get rid of obsolete .changes
   from p-u ['dak clean-proposed-updates *.changes' from within p-u]
 o [also check for obsolete .changes caused by 'dak rm'-ing from p-u]
+o Update dak.conf (at least the section for Reject-Proposed-Updates,
+  before using 'dak reject-proposed-updates')
 o Install, reject and remove packages as directed by the SRM using
   'dak process-accepted' (installs), 'dak reject-proposed-updates'
   (rejects) and 'dak rm' (removals)
@@ -11,25 +13,40 @@ o Install, reject and remove packages as directed by the SRM using
   NB: removing packages are not logged to the stable ChangeLog; you
       need to do that byhand.
 
-o Do anything in proposed-updates/TODO
-o Close any applicable woody bugs
-  (hint: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&include=woody)
-o Update version number in README and dists/README (ftp-master only)
+o If you installed a debian-installer upload; migrate the relevant
+  installer-*/$release directory from proposed-updates to stable.
+  (Including potentially removing older versions)
+
+o Decruft stable in coordination with SRMs
+
+o Do anything in proposed-updates/TODO 
+o Close any applicable stable bugs
+  (hint: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&include=etch)
+o Update version number in README, README.html and dists/README
 o Update the 'Debian<n>.<n>r<n>' symlink in dists/
-o Clean up dists/ChangeLog (add header, basically)
-o Update version fields in dak.conf[-non-US]
+o Clean up dists/stable/ChangeLog (add header, basically)
+o Update version fields in dak.conf
 o Update fields in suite table in postgresql (see below)
 
-o Comment out "Untouchable" in dak.conf[-non-US]
-o Run 'dak make-suite-file-list -s stable'
-o Run apt-ftparchive generate apt.conf.stable[-non-US]
-o Run 'dak generate-releases stable'  ** FIXME: requires apt.conf.stable stanza for stable in apt.conf
-                    ** FIXME: must be run as dak
-o Uncomment "Untouchable" in dak.conf[-non-US]
+o Run 'dak make-suite-file-list --force -s stable'
+o Run apt-ftparchive generate apt.conf.stable
+o Run 'dak generate-releases --force-touch --apt-conf apt.conf.stable stable'
 
-Yes, this sucks and more of it should be automated.
+[Yes, this sucks and more of it should be automated. c.f. ~ajt/pointupdate]
 
 #######################################################
 
-update suite set version = '3.0r4' where suite_name = 'stable';
-update suite set description = 'Debian 3.0r4 Released 31st December 2004' where suite_name = 'stable';
+update suite set version = '4.0r3' where suite_name = 'stable';
+update suite set description = 'Debian 4.0r3 Released 16th February 2008' where suite_name = 'stable';
+
+Rough Guide to doing Old-Stable Point Releases in Debian
+--------------------------------------------------------
+
+Pretty much as above, except that process-accepted doesn't know about
+oldstable, so you have to do some surgery on it first to make it
+support that.  Probably want to disable cron.daily whilst doing so.
+Also watch out for the installing_to_stable detection which doesn't
+work well with the current layout of oldstable-proposed-updates (as a
+symlink to $distro-proposed-updates).  clean-proposed-updates,
+cruft-report and most everything else support a -s/--suite so they
+sould be fine to use.