The-Homebrew-Cloud/dolphin
2
0
Fork 0
mirror of https://github.com/dolphin-emu/dolphin.git synced 2025-01-09 15:49:25 +01:00
Code Issues Packages Projects Releases Wiki Activity

further explain changes to version constants in ScmRevGen

OatmealDome 2024-07-05 17:54:16 -04:00
parent 2304f1d3d1
commit 50754e205f
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Release-Process.md

@ -13,7 +13,10 @@ Releases can only be created by [core developers](https://github.com/orgs/dolphi
* If creating a major release, use the commit that the release should be based on. * If creating a major release, use the commit that the release should be based on.
* If creating a hotfix release, use the tag of the last release. * If creating a hotfix release, use the tag of the last release.
3. Cherry pick any necessary commits. 3. Cherry pick any necessary commits.
4. Update `DOLPHIN_VERSION_MAJOR` and `DOLPHIN_VERSION_MINOR` in `CMake/ScmRevGen.cmake`, and commit the result. 4. Update the version constants in `CMake/ScmRevGen.cmake`, and commit the result.
* Set `DOLPHIN_VERSION_MAJOR` to `YYMM`.
* Set `DOLPHIN_VERSION_MINOR` to the patch number. If creating a hotfix release, use the number corresponding to the patch letter (for example, `a` is `1`, `b` is `2`, etc). Otherwise, set to `0`.
* This field must be set to a number [as CPack does not support non-numerical values in the minor or patch version fields](https://gitlab.kitware.com/cmake/cmake/-/issues/19310).
5. Push the branch to GitHub: `git push -u origin release-prep-YYMM`. 5. Push the branch to GitHub: `git push -u origin release-prep-YYMM`.
6. Smoke test the produced builds. 6. Smoke test the produced builds.
* The builds can be downloaded at `https://dolphin-emu.org/download/list/release-prep-YYMM/1/`. * The builds can be downloaded at `https://dolphin-emu.org/download/list/release-prep-YYMM/1/`.