From 20df5357b17d31a3adc4d6f7cfdd9d4f1c5addf2 Mon Sep 17 00:00:00 2001 From: Andreas Gustafsson Date: Tue, 8 Aug 2000 23:37:21 +0000 Subject: [PATCH] edited --- doc/dev/release | 39 +++++++++++++++------------------------ 1 file changed, 15 insertions(+), 24 deletions(-) diff --git a/doc/dev/release b/doc/dev/release index 88bc1271ac..0e54b29117 100644 --- a/doc/dev/release +++ b/doc/dev/release @@ -1,7 +1,7 @@ Copyright (C) 2000 Internet Software Consortium. See COPYRIGHT in the source root or http://www.isc.org/copyright for terms. -$Id: release,v 1.12 2000/08/01 01:18:24 tale Exp $ +$Id: release,v 1.13 2000/08/08 23:37:21 gson Exp $ Preparing a bind9 release @@ -10,7 +10,7 @@ release. - Update the README file - - Update doc/misc/options + - Update doc/misc/options, verify that doc/misc/dnssec is up-to-date - Verify that the file "version" contains the correct version number (it should have been incremented after the @@ -51,20 +51,11 @@ release. - Announce a CVS pool freeze on bind-dev - - Do basic tests on each build system: + - Run util/altbuild.sh. This is to make sure that builds using libtool, + separate source/object directories, and other obscure build options + work. Save the output and look for error and warning messages. - check out a source tree - do a build - test it: - transfer in - transfer out - auth query - recursive query - exit cleanly with no leaks - - - Do a test build using a separate build directory and libtool - - - Run + - On a system like the one Tale is using (:-)), run the command find lib -name '*.h' -print | xargs perl util/check-includes.pl @@ -85,17 +76,16 @@ release. "cvs rtag v9_0_0b3 bind9" (mainline) or "cvs rtag -r v9_0 v9_0_0rc1 bind9" (release branch). - - Export the source tree in to a fresh directory by - running "cvs export", as in "cvs export -rv9_0_0b3 bind9" - - - Build the kit: + - Build the release kit: + cd + cvs export -r v9_0_0rc2 bind9 cd bind9 sh configure make kit - Build bind9 from the kit on at least one machine - and test it + and test it. - If problems are found at this stage, fix them, move the release tag up using "rtag -F", and respin the kit. @@ -104,7 +94,7 @@ release. and sign them with the ISC signing PGP key: "pgp -sba bind-9.0.0b3.tar.gz -u 0x51BAB2ED" - - Fix the permissions permissions on the signature file: + - Fix the permissions on the signature file: chmod 644 bind-9.0.0b3.tar.gz.asc @@ -118,9 +108,10 @@ release. - Copy the distribution and PGP signature files to the FTP site: - ssh isrv4.pa.vix.com "mkdir /udir/ftp/isc/bind9/9.0.0b4" - scp bind-9.0.0b4.tar.gz bind-9.0.0b4.tar.gz.asc \ - isrv4.pa.vix.com:/udir/ftp/isc/bind9/9.0.0b4 + ver=9.0.0rc2 + ssh isrv4.pa.vix.com "mkdir /udir/ftp/isc/bind9/$ver" + scp bind-$ver.tar.gz bind-$ver.tar.gz.asc \ + isrv4.pa.vix.com:/udir/ftp/isc/bind9/$ver - Download using FTP (or Netscape) and verify the PGP signature again