From 6abd2e93505ebb4839d7bce5e6ca07ab5098961c Mon Sep 17 00:00:00 2001 From: Roger Date: Mon, 19 Dec 2016 02:40:42 -0500 Subject: [PATCH] Linted markdown --- Release-Process.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/Release-Process.md b/Release-Process.md index 52d3cd3..ed4003f 100644 --- a/Release-Process.md +++ b/Release-Process.md @@ -1,12 +1,10 @@ ## Introduction ---- 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. ## Details ---- 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.