You should immediately change the value of the
RELEASE, RELEASE_LAST and
RELEASE_NEXT variables at the top of the
include/data/configure.in script to their
next logical values. For example if the last value of
RELEASE had been 1.10.0
then you should set RELEASE_LAST to
1.10.0 and set RELEASE
to 1.10.1. Don't worry about making a
bad guess for the RELEASE_NEXT value - it can
be changed at any time in the future. The
include/data/configure.in file should be
committed and all developers should be notified that they need
to update their work areas and run the
configure command. This is important! If you
fail to follow this last step and a developer invokes the
make release-tag then the tags in the
CVS repository will no longer agree with the
files in the source tarball which you went to so much trouble to
release (its not the end of the world, just a pain in the
butt).
Here are a few more variables you may need to adjust in the top level configure file:
MANIFEST_FILESYou probably won't need to change this, however, if
you plan on change the number of variations of the
NST to distribute, you will want to
update this list (you will also need to update the
release: target in
include/make/makefile if you add,
remove or modify your variant list).
RELEASE_LAST_MD5You should change this to the MD5
checksum associated with the
src/nst-1.10.0.iso.gz file. You
can find this value near the top of
html/log/release-1.10.0.xml. This
variable is used in the documentation for examples of
verifying the MD5 checksum (things will
still work if you don't update it, but users may be
irritated if they get different results when following
documentation examples).