Public Release

Development

Note: Takes approx 1-2 hours (depending on testing).

1. Create release branch (e.g. v1.2.3), if stable, then branch from tag, else branch from master
2. Do the development work, e.g. commit code etc (do not commit to master)
3. Copy milestone to ChangeLog
4. Ensure version number in CMakeLists.txt is correct
5. Ensure stage name in CMakeLists.txt is correct (stable, beta, etc)
6. Push and wait for buildbot to build (be patient)
7. Wait for packages to be uploaded to webserver
8. Test new bug fixes and features on all operating systems
9. Tag the release branch (branch-stage)
10. Merge release branch into master
11. Delete the release branch
12. Close the release milestone
13. Upload to public website and test links
    1. website@marvin3:/srv/web/symless/public$ ./deploy.sh
    2. ./deploy.sh -b v1.7.5-stable-fa85a24 -r v1.7.5-stable-fa85a24
14. Set current version in website settings in /home/website/website-live
15. Add previous version to alternate downloads by modify php file
16. Install previous version and test update check feature
17. If master: set next version in CMakeLists.txt

Announcement

1. Wait 1 day after deployment
2. Email announcement to entire user list
3. Wait 1 day after email announcement
4. Post on Synergy blog (same as email)
5. Message mailing list (include ChangeLog)
6. Post on the Synergy Forums
7. Post on Facebook page (include blog link)
8. Post on Twitter (include blog link)
9. Post on Google+ page (include blog link)
10. Share on LinkedIn
11. Share on reddit
12. Update Wikipedia version