docs: update release.md with improvements from v3.4.34 release

Signed-off-by: Ivan Valdes <ivan@vald.es>
This commit is contained in:
Ivan Valdes 2024-09-17 13:57:19 -07:00
parent 2ed418c191
commit 7e3901fb04
No known key found for this signature in database
GPG Key ID: 4037D37741ED0CC5

View File

@ -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