X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=docs%2FREADME.stable-point-release;h=c906dabadf1a3b819c3bae183eba15739fb1e8a0;hb=066d01be84db56933591117e616ac35203dffd18;hp=d56689af1cc1d2361b71173fbb759d1a38dc4819;hpb=5fe8b9ec7c70cf888b729f2347579f8630a90833;p=dak.git diff --git a/docs/README.stable-point-release b/docs/README.stable-point-release index d56689af..c906daba 100644 --- a/docs/README.stable-point-release +++ b/docs/README.stable-point-release @@ -1,34 +1,80 @@ Rough Guide to doing Stable Point Releases in Debian ---------------------------------------------------- -o Install, reject and remove packages as directed by the SRM +o Dump projectb for backup purposes. +o get everything listed, dak control-suite -l proposed-updates > p-u.list +o generate the changelog using dak make-changelog +o add everything to stable: cat p-u.list |dak control-suite --add stable +o remove everything from proposed-updates, dak control-suite -r proposed-updates < p-u.list +o sync with stable RM if there is any propup needed. do it, if so. +o ask rms if they have RMs to do. +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 Update version number in README, README.html and dists/README +o Update the 'Debian.r' symlink in dists/ +o Clean up dists/stable/ChangeLog (add header, basically) +o Update fields in suite table in postgresql (see below) + +o Run 'dak dominate --force -s stable' +o Run 'dak generate-filelist -s stable' +o Run apt-ftparchive generate apt.conf.stable +o Run 'dak generate-releases --force-touch --apt-conf apt.conf.stable stable' + + + + +begin; +update suite set version = '5.0.6' where suite_name = 'stable'; +update suite set description = 'Debian 5.0.6 Released 04 September 2010' where suite_name = 'stable'; - NB1: !! you must run katie from within dists/proposed-updates; katie - takes it's "I'm doing a point release" cue from the CWD. !! +------------------------------------------------------------------------ +Old doc: - NB2: removing packages are not logged to the changelog; you need to - do that byhand. + +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) + + NB: removing packages are not logged to the stable ChangeLog; you + need to do that byhand. + + +o Decruft stable in coordination with SRMs o Do anything in proposed-updates/TODO -o Close any applicable potato bugs - (hint: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&include=potato) -o Update version number in README and dists/README (ftp-master only) +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.r' symlink in dists/ -o Clean up dists/ChangeLog (add header, basically) -o Update version fields in katie.conf[-non-US] -o Update fields in suite table in postgresql +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 katie.conf[-non-US] -o Run 'jenna -s stable' -o Run apt-ftparchive generate apt.conf.stable[-non-US] -o Copy tree/directory for stable to apt.conf[-non-US], run ziyi, remove it from apt.conf[-non-US] -o Uncomment "Untouchable" in katie.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 = '2.2r6' where suite_name = 'stable'; -update suite set version = '2.2r7' where suite_name = 'proposed-updates'; -update suite set description = 'Debian 2.2r6 Released 3rd April 2002' where suite_name = 'stable'; -update suite set description = 'Proposed Updates for Debian 2.2r6 - Not Released' where suite_name = 'proposed-updates'; +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.