Deployment Steps

STOP! Have you fully tested the code in stable on your local GAE test site? If not, go away and do so.

1. Switch to the master branch - git checkout master

2. Make sure your branch is up-to-date - git pull origin master

3. In your browser, open up the GAE admin panel to Versions.

4. Open up app.yaml. Application should be 'social-referral'. Version should be 1 larger than the current live version. ie. if you are using 7-56 in the GAE Admin Panel, your app.yaml should say 7-57.

5. DEPLOY! Watch the logs to make sure it all worked properly. If GAE complains that you've reached the max # of versions, go into the GAE Admin Panel and delete the oldest version. Redeploy.

6. Your code isn't live - take a break and relax.

7. Ready to turn it on? Refresh your Version page and turn it on.

8. Have new URL's been deployed? Reload URIs or error messages like Handler does not map to any urls: __X__ will appear.

9. Watch the error logs to see if anything breaks. If it does, switch back to the older Version IMMEDIATELY. Test the new code by visiting a few live sites and playing with the widget. Check error logs. If it looks good, keep the error logs open in a tab and check back every few minutes for edge cases.

10. Pat yourself on the back. Deployment done.

Version Number

Our version numbers follow this format majorVersion-minorVersion. Whenever you release a new feature or major change, increase the majorVersion number (minorVersion will go to 0 to start counting up again).

Hotfixes!

Make sure you merge the hotfix into dev - git checkout dev git pull origin dev git merge master git push origin dev