0N/ACopyright (C) 2000 Internet Software Consortium.
0N/A$Id: release,v 1.17 2000/11/14 18:09:44 gson Exp $
0N/APreparing a bind9 release
0N/AHere's a rough outline of the steps to follow in preparing a new bind9
0N/A - Update the README file
0N/A - Send the new README file to webteam@nominum.com at least 48
0N/A hours prior to the planned release and ask them to prepare
0N/A the web pages for the new version.
0N/A - Verify that the file "version" contains the correct version
0N/A number (it should have been incremented after the
0N/A - Update the lib/*/api files as needed. See the libtool
0N/A info file for information about what the various numbers mean.
0N/A a clean build and test status for all supported systems.
0N/A - Check that "make all_tests" does not produce compile errors.
0N/A - Make sure that the most recent version of the ARM has been
0N/A checked in. Look for any obvious broken links in the
0N/A .html files. If "fgrep .HTML *.html" produces output,
0N/A - Update the copyrights. According to tale:
0N/A Go to the root of the source tree.
0N/A The scripts need to be run from there; they reference the util
0N/A subdirectory internally.
0N/A ... [I prefer to check out a fresh source tree --gson]
0N/A ... examine output, particularly any files with the "?" type, and
0N/A ... examine output, edit as necessary. mail me about anything that
0N/A ... the script should have been able to do itself. :-)
0N/A $ cvs ci -m'update_copyrights'
0N/A - Stop doing pullups.
0N/A obscure build options work. This script may need some hacking if run
0N/A on anything other than NetBSD. Save the output (it's big) and look
0N/A for error and warning messages.
0N/A cd $top_of_mainline_tree
0N/A - If you can (= your system is similar enougn to the on Tale is using),
0N/A check the header files for cruft by running the command
0N/A - Add a marker line like " --- 9.0.0b3 released ---"
0N/A to the CHANGES file.
0N/A - Tag the CVS source tree with the final tag, as in
0N/A "cvs rtag v9_0_0b3 bind9" (mainline) or
0N/A "cvs rtag -r v9_0 v9_0_0rc1 bind9" (release branch).
0N/A - Build the release kit. This procedure differs
0N/A between the 9.0 release branch and the mainline.
0N/A On the release branch,
0N/A cd <temporary directory>
0N/A cvs export -r v9_0_0rc6 bind9
- Build bind9 from the kit on at least one machine
and test it. Run it as a caching name server.
If you can, try resolving some IPv6 addresses and
- 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:
- Fix the permissions on the signature file:
- Verify the PGP signature:
- Prepare a release announcement based on the previous one.
- Copy the distribution and PGP signature files to the FTP site:
- 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 the release on bind-announce@isc.org