-
Notifications
You must be signed in to change notification settings - Fork 185
Release process
Dan Albert edited this page Nov 13, 2021
·
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.
- Tag the release branch when the build is complete. 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. - Smoke test the tagged build
- 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.