Skip to content

Commit 29febff

Browse files
authored
reorder release process in notes (#1829)
Signed-off-by: Zbynek Roubalik <[email protected]>
1 parent b7318e8 commit 29febff

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

RELEASE-PROCESS.MD

+9-9
Original file line numberDiff line numberDiff line change
@@ -5,26 +5,29 @@ The release process of a new version of KEDA involves the following:
55
## 0. Prerequisites
66

77
Look at the last released version in the releases page: https://github.com/kedacore/keda/releases
8-
For example: currently it is 2.0.0
9-
The next version will thus be 2.1.0
8+
For example: currently it is 2.3.0
9+
The next version will thus be 2.4.0
1010

1111
## 1. Changelog
1212

1313
Provide a new section in `CHANGELOG.md` for the new version that is being released along with the new features, patches and deprecations it introduces.
1414

1515
It should not include every single change but solely what matters to our customers, for example issue template that has changed is not important.
1616

17-
## 2. Publish documentation for new version
17+
## 2. Add the new version to GitHub Bug report template
18+
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).
19+
20+
## 3. Publish documentation for new version
1821

1922
Publish documentation for new version on https://keda.sh.
2023

2124
See [docs](https://github.com/kedacore/keda-docs#publishing-a-new-version).
2225

23-
## 3. Create KEDA release on GitHub
26+
## 4. Create KEDA release on GitHub
2427

25-
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).
28+
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).
2629

27-
KEDA Deployment YAML file (eg. keda-2.1.0.yaml) is also automatically created and attached to the Release as part of the workflow.
30+
KEDA Deployment YAML file (eg. keda-2.4.0.yaml) is also automatically created and attached to the Release as part of the workflow.
2831

2932
> Note: The Docker Hub repo with all the different images can be seen here: https://hub.docker.com/r/kedacore/keda/tags
3033
@@ -62,9 +65,6 @@ Learn how to deploy KEDA by reading [our documentation](https://keda.sh/docs/INS
6265
- <list items>
6366
```
6467

65-
## 4. Add the new version to GitHub Bug report template
66-
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).
67-
6868
## 5. Update Helm Charts
6969

7070
Update the `version` and `appVersion` in our [chart definition](https://github.com/kedacore/charts/blob/master/keda/Chart.yaml).

0 commit comments

Comments
 (0)