Plan to release etcd v3.6.0-rc.1

[ivanvc]

What would you like to be added?

We want to release the second release candidate (v3.6.0-rc.1), 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-tbd

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

• [release-3.6] Fix release script prerelease GitHub template release #19420
• [release-3.6] codecov: improve coverage upload #19447
• [release-3.6] Move interface AlarmBackend from server/etcdserver/api/v3alarm to server/storage/schema to fix the unexported-return lint error #19455
• [release-3.6] Backport DowngradeInfo proto change #19471
• [release-3.6] etcdserver: Update description for count field in the RangeResponse message #19468
• [release-3.6] Use RLock in Demoted method for read-only access to expiry #19443
• [release-3.6] depedency: bump golang.org/x/crypto from v0.32.0 to v0.35.0 #19480
• [release-3.6] Fix TestLeaseGrantTimeToLiveExpired flaky due to leader change #19481

Outstanding tasks before releasing this version:

• *: support DowngradeInfo field in maintenence.Status API #19451
• deflake: TestDowngradeCancellationAfterDowngrading1InClusterOf3 #19461

Release team

GitHub handle	Role
@ivanvc	TBD

Link to: #13538

Why is this needed?

To continue the work towards releasing 3.6.0.

[ahrtr]

I am targeting to approve #19451 today, and merge it later today or early tomorrow.

So we should be ready to release rc.1 early next week.

[ivanvc]

If we have #19461 ready by Tuesday, I was thinking of doing this along with 3.4.36. Or should we aim to do them one day apart?

[ahrtr]

If we have #19461 ready by Tuesday, I was thinking of doing this along with 3.4.36

OK to me. So it's Feb 25 (Tuesday)?

[ivanvc]

OK to me. So it's Feb 25 (Tuesday)?

Sorry, I didn't see your message before.

Yes, tomorrow after doing the v3.4 release.

[ivanvc]

Just confirming, @ahrtr, are we set for this release? Or de we have any other blockers?

[ahrtr]

Just confirming, @ahrtr, are we set for this release? Or de we have any other blockers?

We are all ready. No any blockers.