From 946fdb7d23ea2e479f8a6c06c427a6806fc05962 Mon Sep 17 00:00:00 2001 From: Archana Shinde Date: Wed, 19 Feb 2020 18:10:27 -0800 Subject: [PATCH] release: Add documentation mentioning alpha releases We now make alpha releases before making a release candidate release. Mention this in the docs. Fixes #598 Signed-off-by: Archana Shinde --- Stable-Branch-Strategy.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Stable-Branch-Strategy.md b/Stable-Branch-Strategy.md index b809fe1ae..e5e92e7c0 100644 --- a/Stable-Branch-Strategy.md +++ b/Stable-Branch-Strategy.md @@ -51,7 +51,11 @@ is dropped from maintenance. | `stable-1.1` | `1.1.3` | (unmaintained) | Note, the stable-1.1 branch will still exist with tag 1.1.3, but under current plans it is -not maintained further. The next tag applied to master will be 1.4.0-rc0. +not maintained further. The next tag applied to master will be 1.4.0-alpha0. We would then +create a couple of alpha releases gathering features targeted for that particular release (in +this case 1.4.0), followed by a release candidate. The release candidate marks a feature freeze. +A new stable branch is created for the release candidate. Only bug fixes and any security issues +are added to the branch going forward until release 1.4.0 is made. ## Backporting Process