ShuriZma
/
dolphin
mirror of https://github.com/dolphin-emu/dolphin.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

adjust placeholder for version name

OatmealDome 2024-07-05 17:33:00 -04:00
parent 9adf61344d
commit 2304f1d3d1
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Release-Process.md

@ -9,18 +9,18 @@ Releases can only be created by [core developers](https://github.com/orgs/dolphi
## Details
1. Perform a translation sync with Transifex if creating a major release.
2. Create a new branch named `release-prep-xxxx`, where `xxxx` is the version number: `git checkout -b release-prep-xxxx <commit or tag>`
2. Create a new branch named `release-prep-YYMM`: `git checkout -b release-prep-YYMM <commit or tag>`
* 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.
3. Cherry pick any necessary commits.
4. Update `DOLPHIN_VERSION_MAJOR` and `DOLPHIN_VERSION_MINOR` in `CMake/ScmRevGen.cmake`, and commit the result.
5. Push the branch to GitHub: `git push -u origin release-prep-xxxx`.
5. Push the branch to GitHub: `git push -u origin release-prep-YYMM`.
6. Smoke test the produced builds.
* The builds can be downloaded at `https://dolphin-emu.org/download/list/release-prep-xxxx/1/`.
* The builds can be downloaded at `https://dolphin-emu.org/download/list/release-prep-YYMM/1/`.
* Now is the time to fix any last-minute issues. Additional builds can be created by pushing new commits to GitHub.
7. Create an **annotated** tag: `git tag -a xxxx -m "Release for some date"`
8. Push the tag to GitHub: `git push origin xxxx`.
7. Create an **annotated** tag: `git tag -a YYMM -m "Release for some date"`
8. Push the tag to GitHub: `git push origin YYMM`.
9. The release builds will automatically show up on the normal download page.
10. Publish the corresponding Progress Report, if any.
* After publishing, post the link to the Progress Report onto Twitter, Mastodon, Bluesky, etc.
11. Merge the release branch back into master: `git checkout master`, `git merge --no-ff xxxx`
11. Merge the release branch back into master: `git checkout master`, `git merge --no-ff release-prep-YYMM`.