From 9e9f775ae2881ac55e487c738bb16b4b627fba16 Mon Sep 17 00:00:00 2001 From: Jim Angel Date: Mon, 13 Dec 2021 02:28:04 -0600 Subject: [PATCH] updating docs --- release-engineering/role-handbooks/branch-manager.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/release-engineering/role-handbooks/branch-manager.md b/release-engineering/role-handbooks/branch-manager.md index d3c52bdcc94..d7294e5c23f 100644 --- a/release-engineering/role-handbooks/branch-manager.md +++ b/release-engineering/role-handbooks/branch-manager.md @@ -163,6 +163,8 @@ In addition to `gcloud,` `gsutil` is required as well. By default, it comes with At the end of a release, Release Managers will need to announce the new release to the community. +> NOTE: ALL OF THE FOLLOWING `krel` COMMANDS RUN AS MOCK (NO CHANGES) BY DEFAULT. No mock (`--nomock`) must be specified for command to execute / take action. This is clear in the output based on the targeted email test groups, but not obvious before running the command. + This can be done in one of two ways: - The `krel announce` sub command -- A [`SENDGRID_API_KEY`](https://sendgrid.com/docs/ui/account-and-settings/api-keys) will need to be configured correctly on your environment for this to work @@ -176,7 +178,7 @@ This can be done in one of two ways: ```shell # Only for the official release: Inform the Google team to complete the corresponding Deb and RPM builds and confirm with them whether Debian and RPM repositories have the packages before sending the email export SENDGRID_API_KEY= -krel announce send --tag vX.Y.0-{alpha,beta,rc}.Z --name "" --name +krel announce send --tag vX.Y.0-{alpha,beta,rc}.Z --name "" --name ``` See the [Release Commands Cheat Sheet](https://github.com/kubernetes/sig-release/blob/master/release-engineering/role-handbooks/patch-release-team.md#release-commands-cheat-sheet) for example commands.