From 46e63b70768e4cfdd34ea3cbd2c19bd8eb764119 Mon Sep 17 00:00:00 2001 From: Dan Albert Date: Sun, 9 Jan 2022 12:37:21 -0800 Subject: [PATCH] Updated Release process (markdown) --- Release-process.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Release-process.md b/Release-process.md index f101ea6..497cf41 100644 --- a/Release-process.md +++ b/Release-process.md @@ -1,8 +1,8 @@ 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 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. \ No newline at end of file +2. 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. +3. Smoke test the tagged build +4. Update the bug templates in .github to allow reporting bugs against the new release. +5. 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. +6. Announce the release in #:loudspeaker:releases in Discord. \ No newline at end of file