[cosmo-dev] steps to push new cosmo release out

[Randy Letness]

There have been a few bugs fixed, mostly ones seen on during hub usage, 
and some security fixes, so its seems worthwhile to push out a cosmo 
0.12 release, which would be a bug fix only release, no new features, no 
schema changes.  Now that we have reduced resources, we need to figure 
out what that involves.  In the past, we would branch the trunk  and 
spin a release candidate from the branch.  That candidate would be 
tested by verifying any bugs fixed in the release, running any automated 
tests, and holding irc qa sessions, before being certified for release.

We no longer have qa resources, so what steps should we take to verify 
the code is ready for release?  At a minimum we verify fixed bugs and 
get all automated tests passing.  That should probably be enough for a 
bugfix release like 0.12.  Any other ideas?  I know in the past all 
testing was done on lab.osaf.us, which is setup exactly like hub.  I 
need to figure out how to update the server with a build.

-Randy