Release Process

For each new version the release process goes like this

1. Update CMakelists.txt project version to the release you want and commit it into master
2. tag the release in git as staging - this will trigger an Appveyor build which will publish windows builds in the Releases page
3. test the released binaries available from the github releases page
4. if no issues are found merge the changes to master, and now tag the intended release, e.g. v0.2.16
5. the new release is available in releases page
6. once the release is complete, update CMakelists.txt again to mark it with 9999 tweak version and commit it to master
7. Remove the staging release from the github release page

Other steps you may want to take post release:

• update the release notes in the github releases page
• update other pkg sources