2N/APreparing a bind9 release
2N/AHere's a rough outline of the steps to follow in preparing a new bind9
2N/A - Update the README file
2N/A - Verify that the file "version" contains the correct version
2N/A number (it should have been incremented after the
2N/A - If this is a final release (not a beta), update the
2N/A lib/*/api files as needed. See the libtool info file
2N/A for information about what the various numbers mean.
2N/A a clean build and test status for all supported systems.
2N/A - Check that "make all_tests" does not produce compile errors.
2N/A - Announce a CVS pool freeze on bind-dev
2N/A - Do basic tests on each build system:
2N/A check out a source tree
2N/A exit cleanly with no leaks
2N/A - On selected platforms, do more detailed tests:
2N/A Using bind9 as a caching server during web surfing
2N/A Resolving IPv6 addresses
2N/A Doing queries over IPv6
2N/A - Add a marker line like " --- 9.0.0b3 released ---"
2N/A to the CHANGES file.
2N/A - Tag the CVS source tree with the final tag, as in
2N/A "cvs rtag v9_0_0b3 bind9".
2N/A - Export the source tree in to a fresh directory by
2N/A running "cvs export", as in "cvs export -rv9_0_0b3 bind9"
2N/A - Run "make kit" (actually, "sh configure && make kit").
2N/A - Take the resulting distribution files to a secure system
2N/A and sign them with the ISC signing PGP key:
2N/A - Change file permissions on the signature file to make sure
2N/A - Build bind9 from the kit on at least one machine
2N/A - Prepare a release announcement based on the previous one
2N/A - Prepare new web site information
2N/A - Verify the PGP signature:
2N/A - Copy the distribution and PGP signature files to the FTP site
2N/A - Download using FTP and verify the PGP signature again
2N/A - Announce the release
2N/A - Increment the version in the file "version"
2N/A - Announce end of CVS pool freeze on bind-dev