From 29febffc1ec32f41836082c587ba860b7c59d3cd Mon Sep 17 00:00:00 2001 From: Zbynek Roubalik <726523+zroubalik@users.noreply.github.com> Date: Thu, 27 May 2021 13:56:11 +0200 Subject: [PATCH] reorder release process in notes (#1829) Signed-off-by: Zbynek Roubalik --- RELEASE-PROCESS.MD | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/RELEASE-PROCESS.MD b/RELEASE-PROCESS.MD index 0a7e460e53e..07586c18e1c 100644 --- a/RELEASE-PROCESS.MD +++ b/RELEASE-PROCESS.MD @@ -5,8 +5,8 @@ The release process of a new version of KEDA involves the following: ## 0. Prerequisites Look at the last released version in the releases page: https://github.com/kedacore/keda/releases -For example: currently it is 2.0.0 -The next version will thus be 2.1.0 +For example: currently it is 2.3.0 +The next version will thus be 2.4.0 ## 1. Changelog @@ -14,17 +14,20 @@ Provide a new section in `CHANGELOG.md` for the new version that is being releas It should not include every single change but solely what matters to our customers, for example issue template that has changed is not important. -## 2. Publish documentation for new version +## 2. Add the new version to GitHub Bug report template +Add the new released version to the list in `KEDA Version` dropdown in [3_bug_report.yml](https://github.com/kedacore/keda/blob/main/.github/ISSUE_TEMPLATE/3_bug_report.yml). + +## 3. Publish documentation for new version Publish documentation for new version on https://keda.sh. See [docs](https://github.com/kedacore/keda-docs#publishing-a-new-version). -## 3. Create KEDA release on GitHub +## 4. Create KEDA release on GitHub -Creating a new release in the releases page (https://github.com/kedacore/keda/releases) will trigger a GitHub workflow which will create a new image with the latest code and tagged with the next version (in this example 2.1.0). +Creating a new release in the releases page (https://github.com/kedacore/keda/releases) will trigger a GitHub workflow which will create a new image with the latest code and tagged with the next version (in this example 2.4.0). -KEDA Deployment YAML file (eg. keda-2.1.0.yaml) is also automatically created and attached to the Release as part of the workflow. +KEDA Deployment YAML file (eg. keda-2.4.0.yaml) is also automatically created and attached to the Release as part of the workflow. > Note: The Docker Hub repo with all the different images can be seen here: https://hub.docker.com/r/kedacore/keda/tags @@ -62,9 +65,6 @@ Learn how to deploy KEDA by reading [our documentation](https://keda.sh/docs/INS - ``` -## 4. Add the new version to GitHub Bug report template -Add the new released version to the list in `KEDA Version` dropdown in [3_bug_report.yml](https://github.com/kedacore/keda/blob/main/.github/ISSUE_TEMPLATE/3_bug_report.yml). - ## 5. Update Helm Charts Update the `version` and `appVersion` in our [chart definition](https://github.com/kedacore/charts/blob/master/keda/Chart.yaml).