From eeeed7d877c6e0e83432d299672bdb349ddc15f1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=97=A0=E9=97=BB?= Date: Tue, 21 Feb 2017 15:24:27 -0500 Subject: [PATCH] Updated Release Cycle (markdown) --- Release-Cycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Release-Cycle.md b/Release-Cycle.md index 69244a8..8692198 100644 --- a/Release-Cycle.md +++ b/Release-Cycle.md @@ -8,7 +8,7 @@ The main purpose of this document is to design a pattern to make every minor rel ## Release -The first release candidate of a minor version is on **Third Tuesday of Every Month**, the `develop` branch will be merged to `master` branch. After the first RC is published, bug fixes will be all going to branch `release/{major.minor}`, e.g. `release/0.10`. Then the cycle goes into two directions: +The first release candidate of a minor version is on **Third Tuesday of Every Month**, the `develop` branch will be merged to `master` branch. After the first RC is published, the cycle goes into two directions: 1. If there is no critical bug fix for on-going minor release, official release will be published on **next Tuesday**. 2. If there are critical bug fixes for on-going minor release, next version of RC (RC -> RC2, RC2 -> RC3) will be published instead on **next Tuesday**.