Plan to release etcd v3.4.35

[ivanvc]

What would you like to be added?

The etcd patch release criteria has been met for our release-3.4 stable release branch so we should release v3.4.35.

The list of commits included since the previous release is: v3.4.34...release-3.4:

• [3.4] chore(e2e): backport TestNoErrorLogsDuringNormalOperations test #18809
• [3.4] fix(defrag): handle errors during defrag #18843
• [3.4] release: push tag after creating it #18587
• [3.4] Bump go version to 1.22.8 #18670
• [3.4] github/workflows: use ECR mirror for Trivy's DB #18688
• [3.4] [serverWatchStream] terminate recvLoop on sws.close() #18785

Work in progress CHANGELOG is: https://github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-3.4.md#v3435-tbc

List of pull requests we still need to backport from main to release-3.4 before the patch release is issued:

• Use GitHub's CLI gh to publish releases #18604
  • [3.4] release: use GitHub's gh to create GitHub release #18878
• release: properly change working dir if tmp location already exists #18812
  • [3.4] release: properly change working dir if tmp location already exists #18877

Release team

GitHub handle	Role
@jmhbnz	Release Advisor
@ivanvc	Release Lead
@ArkaSaha30	Release Shadow
@henrybear327	Release Shadow

Why is this needed?

Regular patch releases are vital to ensure our users have bug-free and secure software.

[ivanvc]

As discussed on Slack, it would be an excellent opportunity to do the release in person next week at KubeCon.

[ivanvc]

We should update to Go 1.22.9 (#18847)

[ivanvc]

I volunteer to be either the release lead or a shadow.

[ghouscht]

I volunteer to help as a shadow. However I'm not at KubeCon and the timezone difference to central europe might complicate things. If you find someone else to help, I'd be happy to renounce.

[henrybear327]

I volunteer to help as a shadow, too! Same timezone as @ghouscht (Zurich)

[ArkaSaha30]

I want to volunteer as a shadow for the release 🤚

[jmhbnz]

Discussed during sig-etcd triage meeting. We are looking at Tuesday next week MST timezone for the release. Team has been updated above.

Team please confirm if you could make a time for around 09:00 on Tuesday Utah time?

[ivanvc]

9:00 am MT sounds good to me.

Edit: But I think we should release v3.5.17 first (#18846). So, it may be actually more like 10 am MT?

[ivanvc]

@jmhbnz, should we schedule 3.5 at 9 am and 3.4 at 10 am?

[ivanvc]

Can you help me do a pass at issues and PRs that may need backporting since 3.4.34 (September 11th)?

• https://github.com/etcd-io/etcd/issues?q=is%3Aissue+created%3A%3E2024-09-11
• https://github.com/etcd-io/etcd/pulls?q=is%3Apr+base%3Amain+created%3A%3E2024-09-11

I'll also do a pass later this weekend.

[ivanvc]

I swept through issues/PR and added the ones that caught my eye (which, in this case, were actually just mine 😅). Please let me know if you think there are more we should consider.

[ArkaSaha30]

We ran into https issue while committing the release and the fix for it is a backport.

[ivanvc]

The release script incorrectly tagged the GitHub release as "latest". The CLI documentation is not explicit. After researching, I found that the HTML mentions to set --latest=false (ref: https://cli.github.com/manual/gh_release_create). I'll open a pull request myself, as I want to verify that it works on my fork.

Edit: It was due to an old github-cli version. However, updating to the latest didn't have an effect.

[ivanvc]

I'll track the gh release issues/findings at #18604.

[ivanvc]

Thanks, team (@henrybear327, @ArkaSaha30, @jmhbnz), with all follow-up tasks closed and the release in place. I'll go ahead and close this issue 🎉