hpoj release process

- If desired, write the release announcement in advance, but don't send it
  out prematurely!
- Review documentation and TODO list, make and check in any last-minute
  changes.
- Run "cvs update" in all sandboxes (home, work) to make sure I checked
  in everything.

- In the top-level hpoj sandbox directory, run "cvs tag hpoj-0_91" (or whatever
  version I'm currently releasing).
- Still in the hpoj directory, run "cvs export -r hpoj-0_91 -d hpoj-0.91 hpoj",
  adjusting for the revision, of course.
- Run "mv hpoj-0.91 ~".
- In the hpoj-0.91 directory, add something like the following line after
  the first line in the README file:
  "This is hpoj version 0.91, released on November 5, 2003."
- In the parent (home) directory, run the command
  "tar czvf hpoj-0.91.tgz hpoj-0.91".
- Run the command "tar tvfz hpoj-0.91.tgz", make sure it looks right.

- "scp hpoj-0.91.tgz paschal@hpoj.sf.net:htdocs/_download" (only for backup
  purposes in case the SF file-release page is broken).
  Note that in my home directory on the shell server, I have a symlink
  "htdocs" that points to "/home/groups/h/hp/hpoj/htdocs", on which the
  above scp command depends.

- FTP hpoj-0.91.tgz (binary mode!) to upload.sf.net

- Web into the "Admin" section of the SourceForge-supplied hpoj project page.
- Click on "Edit/Release files".
- Click on "quick release a file".
- Select package ID "hpoj"
- Release name "hpoj-0.91"
- Status active
- Filename hpoj-0.91.tgz
- File type Source .gz
- Processor type Any

- Add link from download.shtml to .tgz file on SF file-release page (so that
  downloads will be counted).
- Update website appropriately for new release.
- Send announcement to hpoj-announce.
- Finish website updates as needed.

- Update freshmeat.net release page for hpoj.