Release process

New development should be done on master and always with the next release's version number in all docs and configuration files. Once ready to test the migration/install:

1. Verify all unit tests pass
2. Verify it works in supported browsers
3. Create a release branch: git branch x.y.z
4. Check it out: git checkout x.y.z
5. Push it upstream to deploy off of: git push origin x.y.z
6. Write/test/commit migration script
7. Add upgrade documentation to docs/upgrades.rst.
8. Generate an AMI for the release (remove ~/setup_panda.sh and PANDA public SSH key before imaging)
9. Make new AMI public.
10. Update docs/amazon.rst with new AMI id
11. Update docs/index.rst to remove development version disclaimer
12. Switch back to the master branch: git checkout master
13. Merge in changes from the release branch: git merge x.y.z
14. Push changes upstream: git push
15. Flag x.y.z version branch for doc building on RTFD
16. Update to next version number in setup_panda.sh
17. Update to next version number in docs/conf.py
18. Update to next version number in config/settings.py
19. Update to next version number in CHANGELOG
20. Update docs to reference the next version number in URLs
21. Add new development version disclaimer to docs
22. Commit next version: git commit -am "Rev to version a.b.c for development."
23. Push next version upstream: git push
24. Make release announcements on the mailing list and Twitter