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

Linted markdown

Roger 2016-12-19 02:40:42 -05:00
parent fd6457989a
commit 6abd2e9350
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Release-Process.md

@ -1,12 +1,10 @@
## Introduction ## Introduction
---
Doing a Dolphin Release does require some steps, but if you know what to do it's fairly straightforward. Doing a Dolphin Release does require some steps, but if you know what to do it's fairly straightforward.
Releases are supposed to be tagged on the "stable" branch. Whenever a major release is about to be released, the "master" branch needs to be merged into "stable". For hotfix releases, the important commits should be cherry-picked manually from master. Releases are supposed to be tagged on the "stable" branch. Whenever a major release is about to be released, the "master" branch needs to be merged into "stable". For hotfix releases, the important commits should be cherry-picked manually from master.
## Details ## Details
---
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. Switch the Dolphin i18n Bot to the 'stable' branch to make sure the stable release is being translated. 2. Switch the Dolphin i18n Bot to the 'stable' branch to make sure the stable release is being translated.