Updated Release Process (markdown)
parent
56763a2313
commit
98c4c5e4db
|
@ -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.
|
||||
2. Switch the Dolphin i18n Bot to the 'stable' branch to make sure the next release is still being translated.
|
||||
2. Switch the Dolphin i18n Bot to the 'stable' branch to make sure the stable release is being translated.
|
||||
3. 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.
|
||||
4. Update `PRODUCT_VERSION` in `Installer/Installer.nsi`. And update the `DOLPHIN_VERSION_MAJOR` and `DOLPHIN_VERSION_MINOR` lines in `CMakeLists.txt`.
|
||||
5. Create an **annotated** tag named after the version number.
|
||||
|
|
Loading…
Reference in New Issue