edited

doc/dev/release

@@ -1,7 +1,7 @@
 Copyright (C) 2000, 2001  Internet Software Consortium.
 See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
 
-$Id: release,v 1.22 2001/01/09 21:47:03 bwelling Exp $
+$Id: release,v 1.23 2001/01/18 02:40:39 gson Exp $
 
 Preparing a bind9 release
 
@@ -21,6 +21,8 @@ release.
  - Update the lib/*/api files as needed.  See the libtool 
    info file for information about what the various numbers mean.
 
+ - Do a "cvs update" to check that all changes have been committed.
+
  - Check that http://status.isc.org/bind9/bind9.html shows
    a clean build and test status for all supported systems.
 
@@ -75,7 +77,8 @@ release.
 
  - Ensure that the JPNIC patch applies cleanly:
 
-   XXX This is impacted by sanitize.pl
+   If you don't have the "iconv" library, you need to get it from
+   http://clisp.cons.org/~haible/packages-libiconv.html and install it.
 
    $ sh util/sanitize_all.sh
    $ patch -p0 < contrib/idn/mdnkit/patch/bind9/patch.most > patch.out 2>&1
@@ -119,11 +122,11 @@ release.
    $ mv $patchd/patch.most.new $patchd
    $ cvs ci -ko $patchd/patch.*
 
- - Add a marker line like "	--- 9.0.0b3 released ---"
+ - Add a marker line like "	--- 9.0.0rc1 released ---"
    to the CHANGES file.
 
  - Tag the CVS source tree with the final tag, as in
-   "cvs rtag v9_0_0b3 bind9" (mainline) or
+   "cvs rtag v9_0_0rc1 bind9" (mainline) or
    "cvs rtag -r v9_0 v9_0_0rc1 bind9" (release branch).
 
  - Build the release kit.  This procedure differs
@@ -136,7 +139,8 @@ release.
 	sh configure
 	make kit
 
-   On the mainline, use the "util/kit.sh" script.
+   On the 9.1 release branchy or mainline, use the
+   "util/kit.sh" script.
 
  - Build bind9 from the kit on at least one machine
    and test it.  Run it as a caching name server.
@@ -146,24 +150,23 @@ release.
  - If problems are found at this stage, fix them, move the
    release tag up using "rtag -F", and respin the kit.
 
- - Take the resulting distribution files to a secure system
-   and sign them with the ISC signing PGP key:
+ - Sign the distribution files with the ISC signing PGP key:
 
-   	pgp -sba bind-9.1.0b1.tar.gz -u 0x51BAB2ED
+   	pgp -sba bind-9.1.0rc1.tar.gz -u 0x51BAB2ED
 
  - Fix the permissions on the signature file:
 
-	chmod 644 bind-9.1.0b1.tar.gz.asc
+	chmod 644 bind-9.1.0rc1.tar.gz.asc
 
  - Verify the PGP signature:
 
-	pgp bind-9.1.0b1.tar.gz.asc bind-9.1.0b1.tar.gz
+	pgp bind-9.1.0rc1.tar.gz.asc bind-9.1.0rc1.tar.gz
 
  - Prepare a release announcement based on the previous one.
 
  - Copy the distribution and PGP signature files to the FTP site:
 
-     ver=9.1.0b1
+     ver=9.1.0rc1
      ssh -n 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