Trivial cleanups and rough old stable notes

diff --git a/docs/README.stable-point-release b/docs/README.stable-point-release
index d2dce4648ceb899a7723512b15cddaf65f26e01b..176b33eb89d9c2aa3317ed9ad71639b7a847b4f7 100644 (file)
--- a/docs/README.stable-point-release
+++ b/docs/README.stable-point-release
@@ -19,9 +19,10 @@ o If you installed a debian-installer upload; migrate the relevant
 
 o Decruft stable in coordination with SRMs
 
-o Do anything in proposed-updates/TODO o Close any applicable stable bugs
+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 (ftp-master only)
+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/stable/ChangeLog (add header, basically)
 o Update version fields in dak.conf
@@ -37,3 +38,15 @@ o Run 'dak generate-releases --force-touch --apt-conf apt.conf.stable 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.