Plan to release v3.6.6
What would you like to be added?
The etcd patch release criteria has been met for our release-3.6 stable branch, so we should release v3.6.6.
Work in progress CHANGELOG is: https://github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-3.6.md#v366-tba
The list of commits included since the previous release is: v3.6.5...release-3.6:
- #20707
- #20749
- #20790
- #20801
- #20874
- #20896
- #20901
- #20905
Outstanding tasks before releasing this version:
- None
Release team
| GitHub handle | Role |
|---|---|
| @ivanvc | TBD |
Why is this needed?
Regular patch releases are vital to ensure our users have bug-free and secure software.
Tentative release date: Monday, November 10th (KubeCon Monday).
We're planning on doing this release at KubeCon in the etcd kiosk on Tuesday, November 11th at 4:00 pm ET. We'll have @serathius and @siyuanfoundation there, so they can function as shadows. Also, inviting @upodroid for an initial exploration on automating our releases.
We need to bump etcd 3.6.6 on K8s. cc @joshjms @hakman @ivanvc
@ahrtr I will work on it.
@ahrtr I will work on it.
thx, please follow https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/bump_etcd_version_k8s.md
ALso refer to https://github.com/etcd-io/etcd/pull/20936. We bump etcd 3.6.x to Kubernetes 1.34 and any new minor version (including master).
@yashsingh74 also FYI. @joshjms , @hakman @ivanvc and I all have experience on such work. Please raise your questions in slack channel sig-etcd or github comment (under your PR or this ticket) and cc the related experts.
@ahrtr I am closing this. If we need to track dependency update in k8s side, we should create new issue for it. Thanks @ivanvc for that release.
REF: https://github.com/kubernetes/kubernetes/pull/135331
It isn't just only dependencies update. refer to https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/bump_etcd_version_k8s.md
Keeping the ticket open reflects sig-etcd own the task. It's also a good way to track the effort. It's easy to forget if we only raise issue in K8s repo. Note that @joshjms @hakman and I are the people who are most active doing such chores before, and we know the pains.