From fc9f705cc66735df5d4969cee4d6122f4a224347 Mon Sep 17 00:00:00 2001 From: Dan Albert Date: Sat, 13 Nov 2021 15:15:41 -0800 Subject: [PATCH] Updated Release process (markdown) --- Release-process.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/Release-process.md b/Release-process.md index 453b812..8d828ed 100644 --- a/Release-process.md +++ b/Release-process.md @@ -1,9 +1,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`. **Do not create a release.** A release will be created automatically by the GitHub action from the tag. +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. Include the changelog in the description section. +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. \ No newline at end of file