From b04453d38a0844f9e1196bb494fc10b5279f0624 Mon Sep 17 00:00:00 2001 From: Conor Nolan Date: Wed, 16 Oct 2024 09:44:30 +0100 Subject: [PATCH] Update RELEASE_PROCESS.md --- docs/RELEASE_PROCESS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/RELEASE_PROCESS.md b/docs/RELEASE_PROCESS.md index 680ee9f5..85fca03b 100644 --- a/docs/RELEASE_PROCESS.md +++ b/docs/RELEASE_PROCESS.md @@ -14,6 +14,6 @@ Here is a simplified set of steps to create a release for `provider-ceph`. 5. **tag next pre-release**: Run the **Tag Release Candidate** action on the main development branch with `-rc.0` for the next release (e.g. `v0.0.3-rc.0`). ## Release Candidate -Every time there is a merge to `main`, the **Release Candidate Publish and PR** workflow will:: +Every time there is a merge to `main`, the **Release Candidate Publish and PR** workflow will: 1. Create a release candidate package (eg `v0.0.3-rc.0.1.gcbf3f60is`) and publish it on the Upbound market place (Note: release candidates are not visible to the public on the Upbound marketplace). -2. Open a PR against the main development branch, updating the controller version and README to point at the latest release candidate. +2. Open a PR against the main development branch, updating the controller version and README to point at the latest release candidate. Please review/merge this PR to record the release (this PR will not trigger further CI workflows).