From 9131921e932de5936886149aacf52d540231a3aa Mon Sep 17 00:00:00 2001 From: Dan Albert Date: Sun, 5 Feb 2023 14:54:52 -0800 Subject: [PATCH] Updated Release process (markdown) --- Release-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Release-process.md b/Release-process.md index 4630e5f..5674594 100644 --- a/Release-process.md +++ b/Release-process.md @@ -2,7 +2,7 @@ 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. 2. 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 -3. 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. +3. 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. 4. Smoke test the tagged build 5. Update the bug templates in .github to allow reporting bugs against the new release. Old versions should be removed. 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.