-
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
Plans for v3.6.0 release #13538
Comments
The PR pull/13525 is fixing issue issues/13524. I added one more command-line flag "--wait-cluster-ready-timeout". Although it's a bug fix, actually it's a small feature as well. Can we add the fix into 3.6? |
@ahrtr Yes, it should not be a problem to add it to v3.6 . Maybe to clarify, this list is not created to limit continuous development of smaller features, but to make sure that prioritize half finished or must have features. This should allow us to make go/no go decision about starting v3.6 release process. Not being on the list should not impact the ~100 lines of code changes like PRs that you linked. To give perspective downgrades modified more than 5000 lines of code and is maybe 70% done. We need to make sure that it is in acceptable state before releasing it to users. I will not add this issue to this list as I looks almost done, however I think we can add it to v3.6 milestone so it will be tracked. This should allow me to ping on the issue if there would be a chance it slips. |
mark |
As a part of this release we'll also need to make updates to the website (currently the documentation versions are updated on the Minor releases) |
I am trying to understand if the timeline at the top comment is still accurate: was the |
We have still some PRs in flight that should be merged for alpha. They are required to make the major v3.6 features (downgrades and V2 deprecation) testable by users. Remaining PRs/issues:
Hope to get them ready soon. |
Great, thanks for the detailed updated and for the hard work that makes this possible 🙇 |
I don't think this is critical change that would block us, however we can wait if you think you can implement it soon. |
Release v3.6-alpha SGTM:
|
v3.6-alpha SGTM too @serathius THANK you! |
At this moment we are little late in K8s release cycle, with etcd still on alpha state, I don't think we can target K8s v1.24 release. |
Note, further work on v3.6 release will be postponed until action items from v3.5 data inconsistency issue will be addressed. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
Based on v3.6 milestone https://github.com/etcd-io/etcd/milestone/38 release was planned for today December 15. Even though we won't be able to meet this date I think we should start the release process to make sure that we are ready for Kubernetes v1.24 release. Etcd blocks the K8s dependency upgrade including changes like #13361.
I propose to decide on major features that are still are needed for v3.6 release so we can prioritize work on them and know when to cut alpha release. Timeline proposed to make sure that we will make it for K8s v1.24 release which should be expected to happen around April 2022 (4 month release cycle):
This timeline reserves us 1 month for each stage that should be reserved to collecting feedback and releasing additional sub-releases.
Proposed remaining major changes for v3.6 release that need to be finished before release.
Remaining nice to have issues will be tracked in v3.6 milestone
Please recommend any additional changes that should be tracked.
EDIT (by @ahrtr )
See latest summary and plan to release 3.6.
https://docs.google.com/document/d/14PYLcdTyX3jhdBDc6q6WWRceTaIZePauHTWgjHJ0_ZE/edit?tab=t.0
The document work is tracked in etcd-io/website#926
The text was updated successfully, but these errors were encountered: