#33 improve release automation

[Jason Trump]

generating a beet release is an onerous task which would benefit from some basic automation. the current tasks in a release are something like:

easyant clean
easyant meta:release-all
easyant documentation
easyant -Dsubmodule.dirs=core/,utils/ -Dsubmodule.target=report meta:run-all
easyant package-release
easyant package-reports
easyant maven-repository

create release file hierarchy in SF shell
scp release files into SF hierarchy
scp maven repository onto project site
scp build reports onto project site
set file links for docs and reports on project site in SF shell
update install instructions
update checksums
update tutorial
smoke test archive download, tutorial app deployment
post news item to front page

all of which takes several hours and leaves the site in an inconsistent state at several points. at the very least we should be able to achieve:
1. one command line call to easyant to do a complete clean, build, report, and package
2. easyant automation to push all archives to site, unpack, and set links, *with* backup

should also investigate sourcing the MD5 sums for the release from disk, in which case #2 would eliminate the need to update the install page with every release. then we just have some copy editing in Joomla as the only manual step, which is much nicer.