5552N/ACopyright (C) 2004 Internet Systems Consortium, Inc. ("ISC")
5552N/ACopyright (C) 2000-2003 Internet Software Consortium.
5552N/A$Id: release,v 1.57 2004/03/05 05:04:50 marka Exp $
5552N/AHere's a rough outline of the steps to follow in preparing a new bind9
5552N/A - Send the new README file to webteam@nominum.com at least 48
5552N/A hours prior to the planned release and ask them to prepare
5552N/A the web pages for the new version. If there have been only
5552N/A minor changes, send context diffs relative to the previous
5552N/A - Do a "cvs update" to check that all changes have been committed.
5552N/A - Verify that the file "version" contains the correct version
5552N/A number (it should have been incremented after the
5552N/A - If building from a release branch, check that any important
5552N/A bug fixes made on the mainline since the last release have
5552N/A been pulled up. You can do this by comparing the CHANGES
5552N/A running the script from a mainline tree:
5552N/A This will list all bug fixes on the mainline that are not
5552N/A - Before creating a new release branch, update the lib/*/api files
5552N/A as needed. See the libtool info file for information about what
5552N/A shows a clean build and test status for all supported
5552N/A systems and that the tests are actually being run on the
5552N/A version being released (the version can be found in the
5552N/A page behind the "Source tar build" link).
5552N/A - Regenerate the documentation by running "make man" (mainline/9.2)
5552N/A and commit it. Note that not all machines have the
5552N/A necessary XML tools, but at least trebuchet, cuba,
5552N/A and Scanner's machine do. Commit any files that were
5552N/A - Update the copyrights. According to tale:
5552N/A Go to the root of the source tree.
5552N/A The scripts need to be run from there; they reference the util
5552N/A ... [I prefer to check out a fresh source tree --gson]
5552N/A ... examine output, particularly any files with the "?" type, and
5552N/A ... examine output, edit as necessary. mail me about anything that
5552N/A ... the script should have been able to do itself. :-)
5552N/A $ cvs ci -m'update_copyrights'
5552N/A - Announce a CVS freeze if doing an alpha or beta release from
5552N/A the mainline, or stop doing pullups if building from a release branch.
5552N/A obscure build options work. This script may need some hacking if run
5552N/A on anything other than NetBSD. Save the output (it's big) and look
5552N/A for error and warning messages.
5552N/A Alteratively, you can do this after building the kit, by giving
5552N/A - If you can (= your system is similar enough to the one Tale is using),
5552N/A check the header files for cruft by running the command
5552N/A [ This step is quite imperfect and should probably be skipped
5552N/A - Ensure that the JPNIC patch applies cleanly:
5552N/A If you don't have the "iconv" library, you need to get it from
5552N/A All hunks should have applied successfully with no offset or fuzz.
5552N/A If all succeeded but some were offset or had fuzz, the patch will be
5552N/A regenerated at the end of this stage.
5552N/A $ cd ../../.. ; : cd back to top level
5552N/A Generate a fresh copy of the diffs:
5552N/A - Add a marker line like " --- 9.0.0rc10 released ---"
5552N/A - Tag the CVS source tree with the final tag, as in
5552N/A "cvs rtag v9_0_0rc1 bind9" (mainline) or
5552N/A "cvs rtag -r v9_2 v9_2_0rc10 bind9" (release branch).
5552N/A - Build the release kit. This procedure differs
5552N/A between the 9.0 release branch and later versions.
5552N/A cvs export -r v9_0_0rc10 bind9
5552N/A On the 9.[1-2] release branch or mainline, use the
5552N/A - Build bind9 from the kit on ns-ext (phred)
5552N/A and ns-int (rc), install it, and let it run for
5552N/A a day keeping an eye on it for any problems.
5552N/A # kill both the keep-running script and named itself
5552N/A # kill both keep-running scripts and both named9:s
5552N/A - If you can, try resolving some IPv6 addresses and
5552N/A - If problems are found at this stage, fix them, move the
5552N/A release tag up using "rtag -F", and respin the kit.
5552N/A - Sign the distribution files with the ISC signing PGP key
5552N/A and fix the permissions on the signature file:
5552N/A - Verify the PGP signature:
5552N/A (Look for the words "Good signature" in the output.)
5552N/A - If there is a companion binary kit for NT, sign it and verify the
5552N/A - Prepare a release announcement based on the previous one.
5552N/A - Copy the distribution and PGP signature files to the FTP site:
5552N/A - If there is a companion binary kit for NT, copy it, too:
5552N/A - Download using FTP (or a web browser) using the URLs in the release
5552N/A announcement and verify the PGP signature again
5552N/A - Ask webteam@nominum.com to publish the updated web pages
5552N/A - When the web pages are up, announce the release on
5552N/A - Increment the version in the file "version"