294N/ACopyright (C) 2000 Internet Software Consortium.

294N/ASee COPYRIGHT in the source root or http://www.isc.org/copyright for terms.

787N/A

787N/APreparing a bind9 release

294N/A

294N/AHere's a rough outline of the steps to follow in preparing a new bind9

787N/Arelease.

787N/A

787N/A - Update the README file

787N/A

294N/A - Update doc/misc/options

294N/A

294N/A - Verify that the file "version" contains the correct version

294N/A number (it should have been incremented after the

294N/A previous release)

294N/A

294N/A - If this is a final release (not a beta), update the

787N/A lib/*/api files as needed. See the libtool info file

787N/A for information about what the various numbers mean.

787N/A

787N/A - Check that http://status.isc.org/bind9/bind9.html shows

294N/A a clean build and test status for all supported systems.

294N/A

294N/A - Check that "make all_tests" does not produce compile errors.

294N/A

294N/A - Make sure that the most recent version of the ARM has been

294N/A checked in. Look for any obvious broken links in the

294N/A .html files.

787N/A

787N/A - Update the copyrights. According to tale:

787N/A

294N/A Go to the root of the source tree.

294N/A The scripts need to be run from there; they reference the util

294N/A subdirectory internally.

787N/A

294N/A $ make distclean

294N/A $ util/merge_copyrights

294N/A $ diff util/copyrights util/newcopyrights

294N/A ... examine output, particularly any files with the "?" type, and

294N/A ... then edit util/newcopyrights if necessary

294N/A $ mv util/newcopyrights util/copyrights

294N/A $ cvs ci -m'merge_copyrights' util/copyrights

294N/A $ util/update_copyrights < util/copyrights

294N/A $ cvs diff

787N/A ... examine output, edit as necessary. mail me about anything that

787N/A ... the script should have been able to do itself. :-)

294N/A $ cvs ci -m'update_copyrights'

294N/A

294N/A - Announce a CVS pool freeze on bind-dev

294N/A

294N/A - Do basic tests on each build system:

787N/A

787N/A check out a source tree

294N/A do a build

787N/A test it:

294N/A transfer in

787N/A transfer out

787N/A auth query

294N/A recursive query

294N/A exit cleanly with no leaks

787N/A

787N/A - On a system with gcc, run

787N/A

787N/A util/check-includes.pl

787N/A util/check-instincludes.sh

787N/A

787N/A - On selected platforms, do more detailed tests:

787N/A

787N/A Using bind9 as a caching server during web surfing

294N/A Resolving IPv6 addresses

294N/A Doing queries over IPv6

787N/A

294N/A - Add a marker line like " --- 9.0.0b3 released ---"

294N/A to the CHANGES file.

294N/A

294N/A - Tag the CVS source tree with the final tag, as in

787N/A "cvs rtag v9_0_0b3 bind9".

294N/A

294N/A - Export the source tree in to a fresh directory by

294N/A running "cvs export", as in "cvs export -rv9_0_0b3 bind9"

787N/A

294N/A - Run "make kit" (actually, "sh configure && make kit").

294N/A

294N/A - Take the resulting distribution files to a secure system

787N/A and sign them with the ISC signing PGP key:

294N/A "pgp -sba bind-9.0.0b3.tar.gz -u 0x51BAB2ED"

294N/A

294N/A - Change file permissions on the signature file to make sure

294N/A it is not writable

787N/A

294N/A - Build bind9 from the kit on at least one machine

294N/A and test it

787N/A

787N/A - Prepare a release announcement based on the previous one

787N/A

787N/A - Prepare new web site information

787N/A

787N/A - Verify the PGP signature:

787N/A pgp bind-9.0.0b3.tar.gz.asc bind-9.0.0b3.tar.gz

294N/A

294N/A - Copy the distribution and PGP signature files to the FTP site:

787N/A

787N/A ssh isrv4.pa.vix.com "mkdir /udir/ftp/isc/bind9/9.0.0b4"

787N/A scp bind-9.0.0b4.tar.gz bind-9.0.0b4.tar.gz.asc \

787N/A isrv4.pa.vix.com:/udir/ftp/isc/bind9/9.0.0b4

787N/A

787N/A - Download using FTP and verify the PGP signature again

294N/A

294N/A - Increment the version in the file "version"

294N/A

294N/A - Announce end of CVS pool freeze on bind-dev

294N/A

294N/A - Announce the release

294N/A