Prior to creating a release, one should perform the following sanity checks.
In order to perform all of the sanity checks, you will need BOTH your NST development system and a running NST probe.
You should do a CVS update and commit to ensure that you are not missing any outstanding modifications.
Run this from the top level to make certain that you have all of the latest RPM packages released for the base distribution.
Run this from the top level to check the URL locations of the optional packages (and home pages) to verify that the source for the optional packages can still be found at the time of release.
Run this from the top level to make certain that you have all of the optional packages built and installed.
You will need to repeat this test by reconfiguring
your KERVER for each kernel variant (smp
and non-smp) you plan to distribute.
Run this from the top level to check the ownership
on files on the running NST probe with
the IP address specified.
Run this from the top level to check for missing
libraries on the running NST probe with
the IP address specified.
Run this from the top level to check the symbolic links
on the running NST probe with
the IP address specified.
This directory contains the utility programs we
bundle with the NST distribution. You should review these
files and remove the ones that are no longer pertinent. In
particular, there should just be one copy of
"nst-vm-livecd-1.8.1.zip". If
you are missing this file, run: "make
vmware-cfg".
If you haven't been building the PDF version of the documentation, you are not getting a full verification of the XML used to write the documentation. This means that there may be errors or missing parts in the HTML documenation produced. By running make release-pdfs not, the documentation files will be validated and this target will fail if errors are found. Unfortunately, this takes a long time to run.