3832N/ACopyright (C) 2000 Internet Software Consortium.
3832N/A$Id: release,v 1.14 2000/08/09 04:37:34 tale Exp $
3832N/AHere's a rough outline of the steps to follow in preparing a new bind9
3832N/A - Verify that the file "version" contains the correct version
3832N/A number (it should have been incremented after the
3832N/A - If this is a final release (not a beta), update the
3832N/A lib/*/api files as needed. See the libtool info file
3832N/A for information about what the various numbers mean.
3832N/A a clean build and test status for all supported systems.
3832N/A - Check that "make all_tests" does not produce compile errors.
4458N/A - Make sure that the most recent version of the ARM has been
3832N/A checked in. Look for any obvious broken links in the
3832N/A - Update the copyrights. According to tale:
4692N/A Go to the root of the source tree.
4776N/A The scripts need to be run from there; they reference the util
4776N/A ... [I prefer to check out a fresh source tree --gson]
4692N/A ... examine output, particularly any files with the "?" type, and
4692N/A ... examine output, edit as necessary. mail me about anything that
4692N/A ... the script should have been able to do itself. :-)
4692N/A $ cvs ci -m'update_copyrights'
4692N/A - Announce a CVS pool freeze on bind-dev
3832N/A work. Save the output and look for error and warning messages.
3832N/A - On a system like the one Tale is using (:-)), run the command
4458N/A - On a system using gcc, do a "make install" and then
4458N/A - On selected platforms, do more detailed tests:
4458N/A Using bind9 as a caching server during web surfing
3832N/A - Add a marker line like " --- 9.0.0b3 released ---"
4458N/A - Tag the CVS source tree with the final tag, as in
4458N/A "cvs rtag v9_0_0b3 bind9" (mainline) or
4458N/A "cvs rtag -r v9_0 v9_0_0rc1 bind9" (release branch).
5061N/A cvs export -r v9_0_0rc2 bind9
4458N/A - Build bind9 from the kit on at least one machine
4458N/A - If problems are found at this stage, fix them, move the
3832N/A release tag up using "rtag -F", and respin the kit.
3832N/A - Take the resulting distribution files to a secure system
3832N/A and sign them with the ISC signing PGP key:
3832N/A - Fix the permissions on the signature file:
4458N/A - Verify the PGP signature:
4458N/A - Prepare a release announcement based on the previous one
4458N/A - Prepare new web site information
3832N/A - Copy the distribution and PGP signature files to the FTP site:
3832N/A - Download using FTP (or Netscape) and verify the PGP signature again
3832N/A - Increment the version in the file "version"
3832N/A - Announce end of CVS pool freeze on bind-dev