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:

#. Verify all unit tests pass #. Verify it works in supported browsers #. Create a release branch: git branch x.y.z #. Check it out: git checkout x.y.z #. Push it upstream to deploy off of: git push origin x.y.z #. Write/test/commit migration script #. Add upgrade documentation to docs/upgrades.rst. #. If any languages have been added, update jumpstart/views.py and docs/i18n.rst to list them. #. Generate an AMI for the release (remove ~/setup_panda.sh and PANDA public SSH key before imaging) #. Make new AMI public. #. Update docs/amazon.rst with new AMI id #. Update docs/index.rst to remove development version disclaimer #. Switch back to the master branch: git checkout master #. Merge in changes from the release branch: git merge x.y.z #. Push changes upstream: git push #. Flag x.y.z version branch for doc building on RTFD #. Update to next version number in setup_panda.sh #. Update to next version number in docs/conf.py #. Update to next version number in config/settings.py #. Update to next version number in CHANGELOG #. Update to next version number in templates/admin/base_site.html #. Update docs to reference the next version number in URLs #. Add new development version disclaimer to docs #. Commit next version: git commit -am "Rev to version a.b.c for development." #. Push next version upstream: git push #. Make release announcements on the mailing list and Twitter