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 <archana.m.shinde@intel.com>
This commit is contained in:
Archana Shinde
2020-02-19 18:10:27 -08:00
parent ed140f157e
commit 946fdb7d23

View File

@@ -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