From 8dc618bf254f2a0ea8aa86c7069be7a8f40e23d4 Mon Sep 17 00:00:00 2001 From: Wenjia Date: Fri, 19 Jul 2024 22:26:51 -0700 Subject: [PATCH] Update release.md Update release.md based on 3.5.15 release: https://github.com/etcd-io/etcd/issues/18247#issuecomment-2240080965 Signed-off-by: Wenjia Zhang --- Documentation/contributor-guide/release.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/contributor-guide/release.md b/Documentation/contributor-guide/release.md index 138fa2a74d67..5606ee88425f 100644 --- a/Documentation/contributor-guide/release.md +++ b/Documentation/contributor-guide/release.md @@ -79,13 +79,14 @@ which don't need to be executed before releasing each version. under project `etcd-development`, and images are pushed to `quay.io` and `gcr.io`. 5. 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 - Select whether it's a pre-release - Publish the release 6. Announce to the etcd-dev googlegroup - Follow the format of previous release emails sent to etcd-dev@googlegroups.com, see an example below, + Follow the format of previous release emails sent to etcd-dev@googlegroups.com, see an example below. After sending out the email, ask one of the mainterners to approve the email from the pending list. ``` Hello,