From 4f8d407843d13078d1061fa81864360aa36b0aa7 Mon Sep 17 00:00:00 2001 From: Dan Albert Date: Sat, 19 Dec 2020 12:43:44 -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 3c592b9..67180e4 100644 --- a/Release-process.md +++ b/Release-process.md @@ -3,7 +3,7 @@ To release a new version of DCS Liberation: 1. Update changelog and release number in the release branch. 2. Make PR from the release branch to master 3. Merge when the build passes -4. Tag master when the build is complete. Format for release tags is `$MAJOR.$MINOR.$PATCH`. +4. Tag master 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/Khopa/dcs_liberation/releases), promote the tagged build to a release. Include the changelog in the description section. 7. Announce the release in #:loudspeaker:releases in Discord. \ No newline at end of file