Do a Sanity Check

Prior to creating a release, one should perform the following sanity checks.

Note: In order to perform all of the sanity checks, you will need BOTH your NST development system and a running NST probe.

Update/Commit

You should do a CVS update and commit to ensure that you are not missing any outstanding modifications.

Build Yum Repository

Run the following from the top level directory to make certain that you can build and update all the RPM files that make up the NST repository.

make repo-build

Check Package Links

Check the links on the manifest page (you may want to use the Pinger Firefox add-on as it was recently updated to support Firefox 3.5).

Alternatively, we may want to consider making a "make link-check" target to perform a similar test using the URLs from the "pkginfo.xml" files we define.

Will need to discuss this step with Ron.

Run Automated Tests

Run the frolloing from the top level to perform numerous checks on the running NST probe with the IP address specified.

make probe-check HOST=IP

There will be a LOT of output produced. A copy of the output will be saved to the file: "probe-check.log" which may be viewed using the command: "less -R probe-check.log". Make sure the file looks clean (or like you would expect). Make sure you aren't tempted to skip this step. We thought we were OK and skipped this step during the 1.8.1 release and ended up delivering a ISO image with a broken sym-link.