From 2304f1d3d1c835fc67e7572b21837b6d185e43f6 Mon Sep 17 00:00:00 2001 From: OatmealDome Date: Fri, 5 Jul 2024 17:33:00 -0400 Subject: [PATCH] adjust placeholder for version name --- Release-Process.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Release-Process.md b/Release-Process.md index 7ba1531..7805c20 100644 --- a/Release-Process.md +++ b/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 ` +2. Create a new branch named `release-prep-YYMM`: `git checkout -b release-prep-YYMM ` * 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` \ No newline at end of file +11. Merge the release branch back into master: `git checkout master`, `git merge --no-ff release-prep-YYMM`. \ No newline at end of file