From 2c7ca8261fa2c169f5d0a9696fce205d0e903aa7 Mon Sep 17 00:00:00 2001 From: Christian Kotzbauer Date: Thu, 30 Sep 2021 16:52:40 +0200 Subject: [PATCH] doc: some clarification for release-docs Signed-off-by: Christian Kotzbauer --- DEVELOPMENT.md | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 4da87d6cf..2c7f13879 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -187,19 +187,12 @@ Check that `README.md` has an updated compatibility matrix and that the url in the `kubectl` incantation (under "Installation") is updated to the new version you want to release. -### Create a tag on the repo and publish the image +### Create a tag on the repo Before going further, we should freeze the code for a release, by -tagging the code, and publishing its immutable artifact: the kured -docker image. +tagging the code. The Github-Action should start a new job and push +the new image to the registry. -```sh -make DH_ORG="weaveworks" VERSION="1.3.0" image -``` - -Then docker push the image. In the future, that might be automatically -done when creating a tag on the repository, with the help of github -actions. ### Create the combined manifest @@ -237,3 +230,6 @@ A change in the helm chart requires a bump of the `version` in `charts/kured/Chart.yaml` (following the versioning rules). Update it, and issue a PR. Upon merge, that PR will automatically publish the chart to the gh-pages branch. + +When there are open helm-chart PRs which are on hold until the helm-chart has been updated +with the new kured version, they can be merged now (unless a rebase is needed from the contributor).