edited

doc/dev/release

@@ -1,15 +1,13 @@
 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.38 2001/07/06 21:15:10 gson Exp $
+$Id: release,v 1.39 2001/07/14 01:55:39 gson Exp $
 
 Preparing a bind9 release
 
 Here's a rough outline of the steps to follow in preparing a new bind9
 release.
 
- - Do a "cvs update" to check that all changes have been committed.
-
  - Update the README file
 
  - Send the new README file to webteam@nominum.com at least 48
@@ -18,6 +16,8 @@ release.
    minor changes, send context diffs relative to the previous
    release instead.
 
+ - Do a "cvs update" to check that all changes have been committed.
+
  - Verify that the file "version" contains the correct version
    number (it should have been incremented after the
    previous release)
@@ -179,12 +179,12 @@ release.
  - Sign the distribution files with the ISC signing PGP key
    and fix the permissions on the signature file:
   
-   	pgp -sba bind-9.1.3.tar.gz -u 0x51BAB2ED
-	chmod 644 bind-9.1.3.tar.gz.asc
+   	pgp -sba bind-9.2.0a3.tar.gz -u 0x51BAB2ED
+	chmod 644 bind-9.2.0a3.tar.gz.asc
 
  - Verify the PGP signature:
 
-	pgp bind-9.1.3.tar.gz.asc bind-9.1.3.tar.gz
+	pgp bind-9.2.0a3.tar.gz.asc bind-9.2.0a3.tar.gz
 
    (Look for the words "Good signature" in the output.)
 
@@ -192,7 +192,7 @@ release.
 
  - Copy the distribution and PGP signature files to the FTP site:
 
-     ver=9.1.3
+     ver=9.2.0a3
      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