-
Notifications
You must be signed in to change notification settings - Fork 171
Release Process
@equalsraf edited this page Jul 1, 2022
·
2 revisions
For each new version the release process goes like this
- Update CMakelists.txt project version to the release you want and commit it into master
- tag the release in git as staging - this will trigger an Appveyor build which will publish windows builds in the Releases page
- test the released binaries available from the github releases page
- if no issues are found merge the changes to master, and now tag the intended release, e.g. v0.2.16
- the new release is available in releases page
- once the release is complete, update CMakelists.txt again to mark it with 9999 tweak version and commit it to master
Other steps you may want to take post release:
- update the release notes in the github releases page
- update other pkg sources