-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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.5.15 #18247
Comments
After a sweep of fixes merged in the main branch after 3.5.14, I found these two potential backports:
Do we want to backport any of these? I would appreciate another pair of eyes to do another pass. I also volunteer to be a shadow for this release :) |
@spzala or @wenjiaswe did either of you want to lead this release? If not I am happy to volunteer as release lead.
Will do some review soon, we also need to take a close look at recent bug reports and see if anything needs to be included: https://github.com/etcd-io/etcd/issues?q=is%3Aissue+label%3Atype%2Fbug+created%3A%3E%3D2024-04-30 |
We may want to hold the release after 7/2, as according to SIG-release's email
I do see some outstanding changes in the Go Release Dashboard. But I don't know how to check when the version will be released, and I'm not sure if it will come with another vulnerability fix. |
@jmhbnz Yes, I am happy to do the release. It's a short week in US, maybe I can do it next week? |
SGTM - So release team will be:
/assign @wenjiaswe, @ivanvc, @jmhbnz |
Would you guys be available Monday, July 8th, at 11 a.m. PT? I'll be out next week starting Tuesday, so I won't be available if you want to schedule it for later that day, which is fine by me, we could see if someone else wants to shadow :) |
What is the CVE score? NIST don't list it yet https://nvd.nist.gov/vuln/detail/CVE-2024-24791. Our patch release criteria is 7.5 https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/release.md#patch-release-criteria but I'm not opposed to start organising |
That's a good point. I think there's no rush, and ultimately, there are no other outstanding changes for 3.4 other than the Go update. |
I reviewed these and couldn't find anything that caught my eye. |
Have raised backport proposals for both: |
Are we still expecting the 3.5.15 release this week? Thanks. |
We have scheduled this release for today, Friday, July 19th, at 1 pm PT. |
3.5.15 has been published: https://github.com/etcd-io/etcd/releases/tag/v3.5.15 |
Improvement to do before 3.5.16:
|
Update release.md based on 3.5.15 release: #18247 (comment)
Update release.md based on 3.5.15 release: #18247 (comment) Signed-off-by: Wenjia Zhang <wenjiazhang@google.com>
PLease also update the release date, thx https://github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-3.5.md#v3515-tbd |
Done in #18355. |
Update release.md based on 3.5.15 release: #18247 (comment) Signed-off-by: Wenjia Zhang <wenjiazhang@google.com>
Update release.md based on 3.5.15 release: #18247 (comment)
Signed-off-by: Wenjia Zhang <wenjiazhang@google.com>
Update release.md based on 3.5.15 release: #18247 (comment) Signed-off-by: Wenjia Zhang <wenjiazhang@google.com>
All done. |
thx all. |
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 releasev3.5.15
.The list of commits included since the previous release is: v3.5.14...release-3.5:
Work in progress CHANGELOG is: https://github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-3.5.md#v3515-tbd
List of pull requests we still need to backport from
main
torelease-3.5
before the patch release is issued:Why is this needed?
Regular patch releases are vital to ensure our users have bug-free and secure software.
The text was updated successfully, but these errors were encountered: