Skip to content

Commit

Permalink
Updated release-management.md
Browse files Browse the repository at this point in the history
Signed-off-by: ChandanSagar <chandan.pradhan@mayadata.io>
  • Loading branch information
ChandanSagar committed Jul 1, 2019
1 parent af5b4ff commit 269030e
Showing 1 changed file with 7 additions and 6 deletions.
13 changes: 7 additions & 6 deletions contribute/design/release-management.md
Original file line number Diff line number Diff line change
@@ -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).
Expand Down

0 comments on commit 269030e

Please sign in to comment.