Here is a checklist for releasing Testground, as well as the gist of our discussion yesterday with respect to formalising the release process and git branching model during the release period.
FOLLOW UP TODOS:
[ ] add a section on announcements and make sure everyone has access to credentials to publish them, such as twitter, blog posts, email to @shipped, etc.
[ ] maybe we also need a QA section - for example, right now we don't have integration tests for the testground/infra repo, and we do that manually - ./install.sh is automated, so the QA right now is really just about creating a cluster, and making sure that you can schedule a test plan on it.
Here is a checklist for releasing Testground, as well as the gist of our discussion yesterday with respect to formalising the release process and git branching model during the release period.
FOLLOW UP TODOS:
announcementsand make sure everyone has access to credentials to publish them, such as twitter, blog posts, email to@shipped, etc.testground/infrarepo, and we do that manually -./install.shis automated, so the QA right now is really just about creating a cluster, and making sure that you can schedule a test plan on it.