weyne/dcs-retribution
1
0
Fork 0
mirror of https://github.com/dcs-retribution/dcs-retribution.git synced 2025-11-10 15:41:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Release process (markdown)

Dan Albert 2022-01-09 12:37:21 -08:00
parent 5a75d817b3
commit 46e63b7076
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
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.
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.