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. Create a release branch: git branch x.y.z
2. Push it upstream to deploy off of: git push origin x.y.z
3. Write/test/commit migration script
4. Generate an AMI for the release (remove ~/setup_panda.sh before imaging)
5. Update docs/amazon.rst with new AMI id
6. Update docs/index.rst to remove development version disclaimer
7. Switch back to the master branch: git checkout master
8. Merge in changes from the release branch: git merge x.y.z
9. Push changes upstream: git push
10. Flag x.y.z version branch for doc building on RTFD.
11. Update to next version number in setup_panda.sh.
12. Update to next version number in docs/conf.py
13. Update to next version number in config/settings.py
14. Update to next version number in CHANGELOG
15. Update docs to reference the next version number in URLs.
16. Add new development version disclaimer to docs.
17. Commit next version: git commit -am "Rev to version a.b.c for development."
18. Push next version upstream: git push