From 7e3901fb04d5023c16a01ab1b9fed74e51a2c8e2 Mon Sep 17 00:00:00 2001 From: Ivan Valdes Date: Tue, 17 Sep 2024 13:57:19 -0700 Subject: [PATCH] docs: update release.md with improvements from v3.4.34 release Signed-off-by: Ivan Valdes --- Documentation/contributor-guide/release.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/contributor-guide/release.md b/Documentation/contributor-guide/release.md index 5f045540eb4..e5726d00b49 100644 --- a/Documentation/contributor-guide/release.md +++ b/Documentation/contributor-guide/release.md @@ -78,11 +78,14 @@ which don't need to be executed before releasing each version. It generates all release binaries under the directory `/tmp/etcd-release-${VERSION}/etcd/release/` and images. Binaries are pushed to the Google Cloud bucket under project `etcd-development`, and images are pushed to `quay.io` and `gcr.io`. + + **Remove the `quay.io` login entry from `~/.docker/config.json` after pushing Docker images.** 7. Publish the release page on GitHub - Set the release title as the version name - Choose the correct release tag (generated from step #4) - Follow the format of previous release pages - Attach the generated binaries and signature file + - Verify the historical binary size for each architecture. If there's a big difference, verify that it works for that architecture - Select whether it's a pre-release - Publish the release 8. Announce to the etcd-dev googlegroup