Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan to release etcd v3.6.0-rc.1 #19456

Open
2 tasks
ivanvc opened this issue Feb 20, 2025 · 3 comments
Open
2 tasks

Plan to release etcd v3.6.0-rc.1 #19456

ivanvc opened this issue Feb 20, 2025 · 3 comments
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. type/feature

Comments

@ivanvc
Copy link
Member

ivanvc commented Feb 20, 2025

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:

Outstanding tasks before releasing this version:

Release team

GitHub handle Role
@ivanvc TBD

Link to: #13538

Why is this needed?

To continue the work towards releasing 3.6.0.

@ivanvc ivanvc added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. type/feature labels Feb 20, 2025
@ivanvc ivanvc changed the title Plan to release v3.6.0-rc.1 Plan to release etcd v3.6.0-rc.1 Feb 21, 2025
@ahrtr
Copy link
Member

ahrtr commented Feb 21, 2025

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
Copy link
Member Author

ivanvc commented Feb 22, 2025

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
Copy link
Member

ahrtr commented Feb 22, 2025

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)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. type/feature
Development

No branches or pull requests

2 participants