From 4173395fa711577fb4af7ca8d7e63c12464d266a Mon Sep 17 00:00:00 2001 From: Rishabh Bohra Date: Thu, 22 Apr 2021 13:51:11 +0530 Subject: [PATCH] Fix broken links (#1787) Signed-off-by: Rishabh Bohra --- RELEASE.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index eedfc7c16..b6b798aa7 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -79,7 +79,7 @@ The token must grant full access to: `repo`, `write:packages`, `read:packages`. ![img](.github/new-branch.png) 1. Send an announcement email to [kudobuilder@googlegroups.com](https://groups.google.com/forum/#!forum/kudobuilder) with the subject `[ANNOUNCE] Kudo $VERSION is released` 1. Run `./hack/generate_krew.sh` and submit the generated `kudo.yaml` to https://github.com/kubernetes-sigs/krew-index/. -1. Update KUDO_VERSION [in the Makefile](https://github.com/kudobuilder/operators/blob/main/Makefile#L2) of operators repo +1. Update KUDO_VERSION [in the Makefile](https://github.com/kudobuilder/operators/blob/master/Makefile#L2) of operators repo. **Note:** If there are issues with the release, any changes to the repository will result in it being considered "dirty" and not in a state to be released. It is possible outside of the standard release process to build a "snapshot" release using the following command: `goreleaser release --skip-publish --snapshot --rm-dist` @@ -91,7 +91,7 @@ This process will create a `dist` folder with all the build artifacts. The chang ### Cutting a Release Branch -As outlined above, when it is necessary to create a new release branch, it is necessary to update the [circle-ci config](https://github.com/kudobuilder/kudo/blob/main/.circle-ci/config.yml#L13) to test merges against the correct branch. It is necessary replace all references to `main` with the appropriate release branch. +As outlined above, when it is necessary to create a new release branch, it is necessary to update the [circle-ci config](https://github.com/kudobuilder/kudo/blob/main/.circleci/config.yml) to test merges against the correct branch. It is necessary replace all references to `main` with the appropriate release branch. ### Cutting a Patch Release @@ -110,4 +110,4 @@ This is the full pre-release step by step: 1. Invoke goreleaser `goreleaser --rm-dist`. 1. Push only versioned docker image via `docker push kudobuilder/controller:v0.2.0-rc1` -**Note:** The release notes for a pre-release should contain all changes since any previously released version. For example `0.16.0-rc1` should list all changes since `0.15.3` if that was the latest `0.15` release. `0.16.0-rc2` would contain all changes since `0.16.0-rc1`. \ No newline at end of file +**Note:** The release notes for a pre-release should contain all changes since any previously released version. For example `0.16.0-rc1` should list all changes since `0.15.3` if that was the latest `0.15` release. `0.16.0-rc2` would contain all changes since `0.16.0-rc1`.