Plan to release v3.6.0-rc.2

[ivanvc]

What would you like to be added?

We want to release the third release candidate (v3.6.0-rc.2), continuing the plan to release version 3.6.0.

Work in progress CHANGELOG is: https://github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-3.6.md#v360-rc2-tbd

The list of commits included since the previous release is: v3.6.0-rc.1...release-3.6:

• [release-3.6] Add prometheus metric for server feature gate #19495
• [release-3.6] etcdserver: Fixing minor typos in v3election.proto and rpc.proto #19501
• [release-3.6] tests: deflakey TestLeaseGrantKeepAliveOnce #19507

Outstanding tasks before releasing this version:

• Backport Add prometheus metric for server feature gate #19452
• Go v1.23.7
• golang.org/x/net v0.36.0(?)

Release team

GitHub handle	Role
@ivanvc	TBD

Why is this needed?

To continue the work towards releasing 3.6.0.

[ivanvc]

@jmhbnz, looks like we will have another day with two releases (#19494). Are you available to help with them next week? We could swap the advisor/lead role. Or, I'm happy to be the lead again.

[ivanvc]

According to the golang mailing list, Go v1.23.7 will be released next Tuesday, March 4th, along with a new golang.org/x/net version to address CVE-2025-22870. It would be great to ship our latest versions with these version bumps. So, tentatively the releases are due on Wednesday, March 5th.

[Totktonada]

@ivanvc I think I should highlight a recently observed panic to the release team as early as possible. It looks like a 3.6 regression. I've wrote down all the details that I know into #19509.

[ivanvc]

@ahrtr, should we consider #19509 as a blocker? The immediate solution to fix the bug, would be to downgrade github.com/grpc-ecosystem/grpc-gateway/v2 to v2.22.0. I verified that downgrading works.

[ahrtr]

@ahrtr, should we consider #19509 as a blocker?

Let's see what we can achieve tomorrow.

[Totktonada]

I can reveal my scenario if it helps to decide whether a fix is important for next release candidates and the upcoming 3.6.0 release.

The problem is found by a test suite that covers our own etcd client implementation (written on Lua). Once v3.6.0-rc0 is released I've added it into CI scripts and found that watcher related test cases are failing.

I'll exclude the watcher related test cases for etcd 3.6 for now. But I would like to re-verify that everything is good before the etcd release. I would like to have some release candidate that includes the fix (or I can verify some commit before a release). But it is completely OK for me if some next release candidates will be tested excluding the watcher scenarios.