New Slate release setup

[Brian T Rice]

I've added http://slate.tunes.org/downloads/ to keep track of any files we
publish for consumption/releases, and updated the home page links to them.

This lets you see how fresh things are, such as the "slate-current"
snapshots, but it's also lets us quickly add any special builds that
people make (say, for BeOS or something) or contributed libraries
available even if we don't have an obvious place in CVS or the front page
for it (although demo/ could use some improvement :).

Also, I'm seriously considering sub-point releases after 0.2, basically
marking the end of each month with 0.2.1, 0.2.2, etc. to force testing and
cycling of the different coding efforts.

I want to encourage everyone to contribute, since we'll now have good
debugging support (for people who don't want to bother with internals),
and a means to test and recover from errors, which mean unit tests will
make a nice way of showing the functionality contract of a library.

Opinions?

-- 
Brian T. Rice
LOGOS Research and Development
http://tunes.org/~water/