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

Clarify which branch to push fixes to.

Jules Blok 2015-06-10 00:24:09 +02:00
parent e830d2c3aa
commit 501e125779
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Release-Process.md

@ -9,7 +9,7 @@ Releases are supposed to be tagged on the "stable" branch. Whenever a major rele
--- ---
1. Merge master into the 'stable' branch such that after merge "stable == master". All following steps refer to that branch. 1. Merge master into the 'stable' branch such that after merge "stable == master". All following steps refer to that branch.
2. Push regression fixes, these will be merged into master at the end, but may be merged to master during this process. 2. Push regression fixes to the 'stable' branch, these will be merged into master at the end, but may be merged to master during this process.
3. Update `PRODUCT_VERSION` in `Installer/Installer.nsi`. And update the `DOLPHIN_VERSION_MAJOR` and `DOLPHIN_VERSION_MINOR` lines in `CMakeLists.txt`. 3. Update `PRODUCT_VERSION` in `Installer/Installer.nsi`. And update the `DOLPHIN_VERSION_MAJOR` and `DOLPHIN_VERSION_MINOR` lines in `CMakeLists.txt`.
4. Create an **annotated** tag named after the version number. 4. Create an **annotated** tag named after the version number.
5. Perform a **clean** Windows build of the "Release Win32" and "Release x64" configurations. 5. Perform a **clean** Windows build of the "Release Win32" and "Release x64" configurations.