The tip of trunk is "what's live"; the documentation, ugarit.setup,
and ugarit.release-info from there is what gets served to the public
at the canonical URLs.

Do not merge documentation changes onto the trunk until you're
releasing, or the live docs will be ahead of the available version!

How to do a release:

  *  Merge desired changes onto the trunk
  *  Update ugarit.setup to set the new version
  *  Install and test to make sure you didn't break it!
  *  Commit, and tag the commit with the version number
  *  Run ../kitten-technologies/bin/generate-download-page to
     update DOWNLOAD.wiki
  *  Update ugarit.release-info to refer to the new release
  *  Commit again
  *  Announce on Google Plus etc.

See also:

http://www.kitten-technologies.co.uk/project/kitten-technologies/doc/trunk/README.wiki

In future, expand this with a way of tagging a pre-release beta in
Fossil for fossil followers to try out, before we tag it for henrietta.