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 a build and 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. once the new release is available in releases page with all the artifacts - adjust the release notes and check all artifacts are there
6. double check before the next step, releases are IMMUTABLE
7. press "Publish Release"
8. once the release is complete, update CMakelists.txt again to mark it with 9999 tweak version and commit it to master
9. Remove the staging release from the github release page
10. If there is a milestone for the release, close it and close the related tickets

Other steps you may want to take post release:

• update other pkg sources

Nightly Releases

Nightly releases are periodically generated to make artifacts available. The build workflow has a manual trigger maintainers can use to call it manually. Github immutable releases prevent the same commit/release to be done twice.