Merge pull request #18600 from ivanvc/update-release-doc-after-observ…

…ations-from-3.4.34

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

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