-
Notifications
You must be signed in to change notification settings - Fork 185
Release process
Dan Albert edited this page Feb 5, 2023
·
11 revisions
To release a new version of DCS Liberation:
- Make sure the version number and changelog are up to date in the release branch. If the changelog needs to be updated, fix it in develop first and cherry-pick the updates to the release branch so they stay in sync.
- Announce a preview build in #:loudspeaker:preview with the link to the GitHub Action for the specifc branch before creating the Release and wait some time. This allows to get some feedback on the build
- When everything is ready for release tag the corresponding release branch. Format for release tags is
$MAJOR.$MINOR.$PATCH
. Do not create a release. A release will be created automatically by the GitHub action from the tag.git tag 6.1.1 && git push --tags
, for example. - Smoke test the tagged build
- Update the bug templates in .github to allow reporting bugs against the new release. Old versions should be removed.
- In Releases, promote the tagged build to a release. The description should be pre-filled with the changelog.
- Announce the release in #:loudspeaker:releases in Discord.