Plan to release etcd v3.5.16

[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.16.

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

• [3.5] Introduce Kubernetes KV interface to etcd client #18358
• [3.5] build(deps): bump distroless/static-debian11 from 6d31326 to 1dbe426 #18388
• [3.5] Upgrade gofail to v0.2.0 #18395
• [3.5] Cleanup github.com/etcd-io/gofail #18398
• [3.5] Backport migration of OWNERS file #18394
• [3.5] go version bump from 1.21.12 to 1.21.13 #18421
• [3.5] Backport github/workflows: set read-only default permissions to approve workflow #18430
• [3.5] Skip leadership check if the etcd instance is active processing heartbeats #18439
• [3.5] test: extend leaseRevoke and leaseRenew test to support 5 members cluster #18451
• [3.5] Bump go toolchain to 1.22.6 #18446
• [3.5] client/pkg/testutil: update interestingGoroutines #18458
• [3.5] tests/e2e: add e2e test to reproduce issue 18089 #18457
• [3.5] mvcc/*_test.go: should not use duplicate revision.Main for one key #18461
• [3.5] tests/e2e: add test cases related to HashKV #18476
• [3.5] *: keep tombstone if revision == compactAtRev #18474
• [3.5] Bump bbolt to 1.3.11 #18489
• [3.5] Fix passing default GRPC call options in Kubernetes client #18517
• [3.5] Introduce the CompactionSleepInterval flag #18514
• [3.5] update Go to 1.22.7 #18550
• [3.5] Backport TestLessorRenewExtendPileup race condition fix #18570

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:

• add bolt compaction sleep interval #13018
• Update Go main branch to 1.23.1 release branches to 1.22.7 #18548

Release team

GitHub handle	Role
@ivanvc	Release lead
@jmhbnz	Release advisor
@ArkaSaha30	Release shadow
@vivekpatani	Release shadow

Why is this needed?

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

[liangyuanpeng]

how about including #18480 in it.

[JalinWang]

Do you consider this PR merged in 2021?
ref: Why is this needed

[ivanvc]

how about including #18480 in it.

@liangyuanpeng, I think it would be reasonable to add the bbolt version bump. We have #18488 and #18489, which are very close to being merged.

Do you consider this PR merged in 2021? ref: Why is this needed

@JalinWang, being this technically an (experimental) feature, I would like to hear @ahrtr / @serathius thoughts on this.

[ahrtr]

Do you consider this PR merged in 2021? ref: Why is this needed

I have no objection on this. Please also see #13018 (comment)

[ivanvc]

@JalinWang, do you want to help backporting #13018 to release-3.5 (after we merge #18495)?

[JalinWang]

@JalinWang, do you want to help backporting #13018 to release-3.5 (after we merge #18495)?

Sure. I will create a backporting PR per https://github.com/etcd-io/etcd/blob/4d42c0f86ac2762253a804fc5d9e6a25b80ef21b/Documentation/contributor-guide/release.md#patch-version-release (, where says the backporting commits "should be restricted to bug fixes and security patches" ? )

Update: I found the discussion about backporting here. The criteria seems to be not that clear :(

[ivanvc]

@JalinWang, with Benjamin's approval, feel free to do the cherry-pick :)

[ArkaSaha30]

Hello @ivanvc , I would want to shadow the release of v3.5.16

[ivanvc]

Hi team (@ahrtr, @jmhbnz, @serathius, @spzala, @wenjiaswe), similar comment to the one from #18486. Would you want to be part of the release team for 3.5.16? I'm happy to lead this one, too, if needed.

[ivanvc]

Hi @ArkaSaha30, can you help to do a pass on pull requests and issues that need to be backported? I'm using the following search: https://github.com/etcd-io/etcd/issues?page=1&q=is%3Aissue+label%3Atype%2Fbug+created%3A%3E%3D2024-07-20, and https://github.com/etcd-io/etcd/issues?q=is%3Apullrequest+label%3Atype%2Fbug+created%3A%3E%3D2024-07-20.

Thanks!

[jmhbnz]

Thanks for volunteering to lead 3.5.16 and 3.4.34 @ivanvc!

I see @ahrtr has agreed to be release advisor for 3.4.34, I am happy to be release advisor for 3.5.16.

I'm just coming back after being sick so I'll do some scope/backport review soon. Keen to set a date for the release and book in the release call 👍🏻

[ArkaSaha30]

Go 1.22.7 will be released tomorrow(5 September 2024) with CVE fixes, do we need to bump go for v3.5.16 in that case?
ref: https://groups.google.com/g/golang-announce/c/vM0L-2IDlOU/m/R-gi-VMOBQAJ?utm_medium=email&utm_source=footer

[ahrtr]

Go 1.22.7 will be released tomorrow(5 September 2024) with CVE fixes, do we need to bump go for v3.5.16 in that case? ref: https://groups.google.com/g/golang-announce/c/vM0L-2IDlOU/m/R-gi-VMOBQAJ?utm_medium=email&utm_source=footer

Thanks for the reminder. I think we should bump go1.22.7 for both 3.5.x and 3.4.x.

[vivekpatani]

@ivanvc @wenjiaswe I'd like to shadow pls, if possible. Thank you.

[ArkaSaha30]

Go 1.22.7 will be released tomorrow(5 September 2024) with CVE fixes, do we need to bump go for v3.5.16 in that case? ref: https://groups.google.com/g/golang-announce/c/vM0L-2IDlOU/m/R-gi-VMOBQAJ?utm_medium=email&utm_source=footer

Go 1.22.7 has been released a few hours ago: https://groups.google.com/g/golang-dev/c/S9POB9NCTdk/m/b5s3OiTsAQAJ?utm_medium=email&utm_source=footer

[ivanvc]

@ArkaSaha30, thanks for the heads-up. I opened #18548 to track the update.

[ivanvc]

Hi @vivekpatani, I was going to send a Slack message regarding this, but I don't know your username. Could you reach out to me on Slack (ivanvc)? Thanks.

Team (@ArkaSaha30, @jmhbnz, @vivekpatani), I know our time zones are spread, so I will suggest when we use it for our community meetings. Are you available next Tuesday (10th) or Wednesday (11th) at 11 a.m. PT? (which would be 6 a.m. NZST and 11:30 p.m. IST)

[jmhbnz]

Team (@ArkaSaha30, @jmhbnz, @vivekpatani), I know our time zones are spread, so I will suggest when we use it for our community meetings. Are you available next Tuesday (10th) or Wednesday (11th) at 11 a.m. PT? (which would be 6 a.m. NZST and 11:30 p.m. IST)

Sounds great - I can do either of those options 🙂

[ivanvc]

We just released v3.5.16. We found the following improvements to the documentation:

1. Step 5 can be simplified to do a single-branch checkout
2. Step 6 should clarify that the release directory is in /tmp/etcd-release-${VERSION}/etcd/release/
3. Step 8 mention to add the "Release" label to the announcement message

[ArkaSaha30]

We just released v3.5.16. We found the following improvements to the documentation:

1. Step 5 can be simplified to do a single-branch checkout
2. Step 6 should clarify that the release directory is in /tmp/etcd-release-${VERSION}/etcd/release/
3. Step 8 mention to add the "Release" label to the announcement message

I will take it up

[ivanvc]

Closing, as there are no more remaining tasks. The release is here: https://github.com/etcd-io/etcd/releases/tag/v3.5.16