From 269030e6110db0c63096088155952f53c47ef0cd Mon Sep 17 00:00:00 2001 From: ChandanSagar Date: Mon, 1 Jul 2019 17:56:43 +0530 Subject: [PATCH] Updated release-management.md Signed-off-by: ChandanSagar --- contribute/design/release-management.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/contribute/design/release-management.md b/contribute/design/release-management.md index 611b9fe540..8528cac551 100644 --- a/contribute/design/release-management.md +++ b/contribute/design/release-management.md @@ -1,12 +1,13 @@ -OpenEBS Release Managent +# OpenEBS Release Management + OpenEBS Components are released as container images with versioned tags. The release process is triggered by creating a Release Tag on the repository. For major releases, the Release Tag is created on the master branch and for minor release, the release tag is triggered on the corresponding release branch. The release process involves the following stages: -Release Candidate Builds -Update Installer and Documentation -Update the charts like Helm stable and other partner charts. (Rancher, OpenShift, IBM ICP Communty Charts, Netapp NKS Trusted Charts (formerly StackPointCloud), AWS Marketplace) -Update the openebs-operator.yaml -Final Release +- Release Candidate Builds +- Update Installer and Documentation +- Update the charts like Helm stable and other partner charts. (Rancher, OpenShift, IBM ICP Communty Charts, Netapp NKS Trusted Charts (formerly StackPointCloud), AWS Marketplace) +- Update the openebs-operator.yaml +- Final Release Release Candidate Builds On reaching the feature freeze date, the repositories are tagged with "Release-Name-RC1" tag. (Example 1.0.0-RC1).