From 87393d82ed616a713754aacd3c402c8a0b97effc Mon Sep 17 00:00:00 2001 From: Zbynek Roubalik Date: Tue, 13 Feb 2024 17:45:21 +0100 Subject: [PATCH] add KEDA OLM release step Signed-off-by: Zbynek Roubalik --- .github/ISSUE_TEMPLATE/4_release_tracker.md | 1 + RELEASE-PROCESS.md | 8 ++++++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/4_release_tracker.md b/.github/ISSUE_TEMPLATE/4_release_tracker.md index 47238f9a6f0..b8573df0cee 100644 --- a/.github/ISSUE_TEMPLATE/4_release_tracker.md +++ b/.github/ISSUE_TEMPLATE/4_release_tracker.md @@ -32,6 +32,7 @@ We aim to release this release in the week of . - [ ] Publish new documentation version - [ ] Setup continuous container scanning with Snyk - [ ] Prepare & ship Helm chart +- [ ] Create a new issue in [KEDA OLM repository](https://github.com/kedacore/keda-olm-operator/issues/new/choose) - [ ] Prepare next release - [ ] Provide update in Slack - [ ] Tweet about new release diff --git a/RELEASE-PROCESS.md b/RELEASE-PROCESS.md index c361913acd7..2ffb9906b97 100644 --- a/RELEASE-PROCESS.md +++ b/RELEASE-PROCESS.md @@ -117,7 +117,11 @@ Before we can release our new Helm chart version, we need to prepare it: Guidance on how to release it can be found in our [contribution guide](https://github.com/kedacore/charts/blob/master/CONTRIBUTING.md#shipping-a-new-version). -## 8. Prepare next release +## 8. Trigger KEDA OLM release + +Create a new issue in [KEDA OLM repository](https://github.com/kedacore/keda-olm-operator/issues/new/choose) stating that there should be a new release mirroring KEDA core release. + +## 9. Prepare next release As per our [release governance](https://github.com/kedacore/governance/blob/main/RELEASES.md), we need to create a new shipping cycle in our [project settings](https://github.com/orgs/kedacore/projects/2/settings/fields/1647216) with a target date in 3 months after the last cycle. @@ -127,7 +131,7 @@ Lastly, the `Upcoming Release Cycles` overview in `ROADMAP.md` should be updated In case of minor releases, we need to create the version branch (`release/v2.x`) from the release tag which will be used to include any required hotfix in the future. -## 9. Tweet! 🐦 +## 10. Tweet! 🐦 Prepare a tweet with some highlights and send it out on [@kedaorg](https://twitter.com/kedaorg)!