From 5a75d817b3c4aa1f3d99d2fada9938dd1ed4190f Mon Sep 17 00:00:00 2001 From: Dan Albert Date: Sun, 9 Jan 2022 12:36:35 -0800 Subject: [PATCH] Updated Release process (markdown) --- Release-process.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Release-process.md b/Release-process.md index 8d828ed..f101ea6 100644 --- a/Release-process.md +++ b/Release-process.md @@ -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. \ No newline at end of file +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