-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
⚠️ *: stabilize project version 3 #1901
⚠️ *: stabilize project version 3 #1901
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: estroz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
You mentioned that having |
450b417
to
adddb9a
Compare
This is kinda ugly. For how long would we support 3-alpha? How do we tell users to upgrade? I'd rather have a policy of getting rid of alpha/beta versions as soon as the next most stable version is available, and relying on this error message to inform users of an upgrade. @camilamacedo86 this relates to your comment. |
I feel like having go/v2 supporting config v3 will stop us from improving config v3. So I would either leave config 3-alpha as a transition step (at least for some time) or remove go/v2 support for config v3. |
@estroz: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Closing in favor of #1959 |
This PR stabilizes project version 3-alpha as 3.
P.S.: there are a few PRs open that change project structure significantly (#1869, #1899). We may want to forego those changes until project version 4 given the impending v3.0.0 release and stability concerns, or not. Whatever the case, this PR can block until the community feels ready to stabilize.