Updated Release process (markdown)

Dan Albert 2022-01-09 12:36:35 -08:00
parent 45ee698964
commit 5a75d817b3

@ -3,5 +3,6 @@ To release a new version of DCS Liberation:
1. 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.
4. 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.
5. Smoke test the tagged build
6. In [Releases](https://github.com/dcs-liberation/dcs_liberation/releases), promote the tagged build to a release. The description should be pre-filled with the changelog.
7. Announce the release in #:loudspeaker:releases in Discord.
6 Update the bug templates in .github to allow reporting bugs against the new release.
7. In [Releases](https://github.com/dcs-liberation/dcs_liberation/releases), promote the tagged build to a release. The description should be pre-filled with the changelog.
8. Announce the release in #:loudspeaker:releases in Discord.