Plan to release etcd v3.5.17

[ivanvc]

What would you like to be added?

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

The list of commits included since the previous release is: v3.5.16...release-3.5:

• [3.5] docs: remove warning that etcd 3.5.0 was not yet released #18579
• [3.5] Ensure commits are signed in scripts/release.sh #18599
• [3.5] Bump go version to 1.22.8 #18669
• [3.5] github/workflows: use ECR mirror for Trivy's DB #18687
• [3.5] Remove defunct release-3.5 arm64 github actions workflows #18802
• [3.5] [serverWatchStream] terminate recvLoop on sws.close() #18784
• [3.5] manual: Fix risk of a partial write txn being applied #18799
• [3.5] chore(e2e): backport TestNoErrorLogsDuringNormalOperations test #18807
• [3.5] fix(defrag): handle errors during defrag #18842
• [3.5] update go to 1.22.9 #18849
• [3.5] fix(defrag): close temp file in case of error #18854

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

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

• Fix tx buffer inconsistency if there are unordered key writes in one tx. #17263
  • [3.5] Backport fix tx buffer inconsistency if there are unordered key writes in one tx #18861
• add tls min/max version to grpc proxy #18816
  • [3.5] add tls min/max version to grpc proxy #18829
• Use GitHub's CLI gh to publish releases #18604
  • [3.5] release: use GitHub's gh to create GitHub release #18876
• release: properly change working dir if tmp location already exists #18812
  • [3.5] release: properly change working dir if tmp location already exists #18863

Release team

GitHub handle	Role
@jmhbnz	Release Advisor
@ivanvc	Release Lead
@ghouscht	Release Shadow
@stackbaek	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.

[jmhbnz]

Discussed during sig-etcd triage meeting. Thanks @ghouscht for volunteering as shadow, I will volunteer as release advisor and with @ivanvc as release lead we are all set to go. We are looking at Tuesday next week MST timezone.

We are thinking early morning on that Tuesday Utah time, how would that work for you @ghouscht?

[stackbaek]

@ivanvc - I'd like to be a release shadow for 3.5.

[ghouscht]

Discussed during sig-etcd triage meeting. Thanks @ghouscht for volunteering as shadow, I will volunteer as release advisor and with @ivanvc as release lead we are all set to go. We are looking at Tuesday next week MST timezone.

We are thinking early morning on that Tuesday Utah time, how would that work for you @ghouscht?

Yes, that does work for me 👍🏻

[ivanvc]

Tentatively, the release will be done at 9:00 am MST.