sandev release process

Here's what we currently do when creating a release:

1. Verify all work for the release is complete and tested.
2. Verify we are using recent Ant and container releases.
3. Verify sand/readme.html is still accurate.
4. Manually drop all tables in the database.
5. Nuke the entire source code tree from a development box, check out the sand module from CVS, and make sure a fresh build is clean.
6. Smoke test the app:
   • Verify the root starts, and the demo app nodes come up, including initial comms and database setup/verification.
   • Make sure the config editor comes up.
   • Make sure the control panel comes up, including drilldown into one of the running nodes.
   • Make sure the TaskHeapDemo UI comes up
7. Tag the tree in CVS as sandev_x_y (select sand, Modify|Create a tag on selection)
8. ant publish.docs (publishes the release documentation)
9. ant publish.release (srubs and creates the release file)
10. Log on to sourceforge and create the release. Post the release text into the release notes and a corresponding news item. Preserve the preformatted text so the line breaks come through.
11. After the files all post (it can take a few minutes for them to show up), verify the news is readable and download the release file onto a clean box. Build and run to make sure nothing was lost in transit except the CVS directories.
12. Update mainbuild.xml with the next release number, and reset release.txt for the next release.