How to Release Code - hyschive/gamer-fork GitHub Wiki
Major/Minor release
In this example, we release version gamer-2.3.0, with the previous version being gamer-2.2.1.
- Create a new branch
v2.3.x - Bump
VERSIONfromgamer-2.3.devtogamer-2.4.devininclude/Macro.hat themainbranch - Bump
VERSIONfromgamer-2.3.devtogamer-2.3.0ininclude/Macro.hat thev2.3.xbranch - Go to
Release/images/Release.png - Click
Draft a new release/images/DraftANewRelease.png - Create a new tag
gamer-2.3.0and selectv2.3.xas the target branch /images/ChooseNewTag.png - Click
Generate release notes; polish the content if needed /images/GenerateReleaseNote_Major_Minor.png - Add the release title
GAMER 2.3.0 - Click
Publish release/images/PublishRelease.png
Maintenance release
In this example, we release version gamer-2.2.2, with the previous version being gamer-2.2.1.
- Cherry-pick the necessary commits from the latest
mainbranch intov2.2.x - Bump
VERSIONfromgamer-2.2.1togamer-2.2.2ininclude/Macro.hat thev2.2.xbranch - Go to
Release/images/Release.png - Click
Draft a new release/images/DraftANewRelease.png - Create a new tag
gamer-2.2.2and selectv2.2.xas the target branch /images/ChooseNewTag.png - Click
Generate release notes; polish the content if needed /images/GenerateReleaseNote_Maintenance.png - Add the release title
GAMER 2.2.2 - Click
Publish release/images/PublishRelease.png