Copyright (C) 2000 Internet Software Consortium.
See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
-$Id: release,v 1.15 2000/09/08 21:27:47 gson Exp $
+$Id: release,v 1.16 2000/09/22 17:50:56 gson Exp $
Preparing a bind9 release
- Update the README file
- - Update doc/misc/options, verify that doc/misc/dnssec is up-to-date
+ - Send the new README file to webteam@nominum.com at least 48
+ hours prior to the planned release and ask them to prepare
+ the web pages for the new version.
- Verify that the file "version" contains the correct version
number (it should have been incremented after the
.html files. If "fgrep .HTML *.html" produces output,
there is a problem.
+ - Verify that the documents in doc/misc are up-to-date
+
- Update the copyrights. According to tale:
Go to the root of the source tree.
... the script should have been able to do itself. :-)
$ cvs ci -m'update_copyrights'
- - Announce a CVS pool freeze on bind-dev
+ - Stop doing pullups
- Run util/altbuild.sh (from the mainline). This is to make sure that
builds using libtool, separate source/object directories, and other
- obscure build options work. Save the output (it's big) and look
+ obscure build options work. This script may need some hacking if run
+ on anything other than NetBSD. Save the output (it's big) and look
for error and warning messages.
cd $top_of_mainline_tree
sh util/altbuild.sh v9_0
- - On a system like the one Tale is using (:-)), run the command
+ - If you can (= your system is similar enougn to the on Tale is using),
+ check the header files for cruft by running the command
find lib -name '*.h' -print | xargs perl util/check-includes.pl
- - On a system using gcc, do a "make install" and then
-
- util/check-instincludes.sh $prefix
-
- - On selected platforms, do more detailed tests:
-
- Using bind9 as a caching server during web surfing
- Resolving IPv6 addresses
- Doing queries over IPv6
-
- Add a marker line like " --- 9.0.0b3 released ---"
to the CHANGES file.
"cvs rtag v9_0_0b3 bind9" (mainline) or
"cvs rtag -r v9_0 v9_0_0rc1 bind9" (release branch).
- - Build the release kit:
+ - Build the release kit. This procedure differs
+ between the 9.0 release branch and the mainline.
+ On the release branch,
cd <temporary directory>
- cvs export -r v9_0_0rc3 bind9
+ cvs export -r v9_0_0rc6 bind9
cd bind9
sh configure
make kit
+ On the mainline, use the "util/kit.sh" script.
+
- Build bind9 from the kit on at least one machine
- and test it.
+ and test it. Run it as a caching name server.
+ If you can, try resolving some IPv6 addresses and
+ doing queries over IPv6.
- If problems are found at this stage, fix them, move the
release tag up using "rtag -F", and respin the kit.
pgp bind-9.0.0rc5.tar.gz.asc bind-9.0.0rc5.tar.gz
- - Prepare a release announcement based on the previous one
-
- - Prepare new web site information
+ - Prepare a release announcement based on the previous one.
- Copy the distribution and PGP signature files to the FTP site:
- ver=9.0.0rc5
- ssh isrv4.pa.vix.com "mkdir /udir/ftp/isc/bind9/$ver"
+ ver=9.0.0
+ 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
- - Download using FTP (or Netscape) and verify the PGP signature again
+ - Download using FTP (or Netscape) using the URLs in the release
+ announcement and verify the PGP signature again
- Increment the version in the file "version"
- - Announce end of CVS pool freeze on bind-dev
+ - Resume doing pullups
+
+ - Announce the release on bind-announce@isc.org
- - Announce the release