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 v3.6.0-rc.2 #19489

Open
1 of 3 tasks
ivanvc opened this issue Feb 26, 2025 · 2 comments
Open
1 of 3 tasks

Plan to release v3.6.0-rc.2 #19489

ivanvc opened this issue Feb 26, 2025 · 2 comments
Assignees
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 26, 2025

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:

Outstanding tasks before releasing this version:

Release team

GitHub handle Role
@ivanvc TBD

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 26, 2025
@ivanvc ivanvc self-assigned this Feb 26, 2025
@ivanvc
Copy link
Member Author

ivanvc commented Feb 26, 2025

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

ivanvc commented Feb 28, 2025

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.

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

1 participant