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

v2 API deprecations imply a breaking v3 change #10356

Closed
htuch opened this issue Mar 12, 2020 · 2 comments
Closed

v2 API deprecations imply a breaking v3 change #10356

htuch opened this issue Mar 12, 2020 · 2 comments
Assignees
Labels
api/v3 Major version release @ end of Q3 2019 bug help wanted Needs help! priority/high

Comments

@htuch
Copy link
Member

htuch commented Mar 12, 2020

As things currently stand, since v2 is canonical and v3 is generated, applying the deprecation removal, any new v2 deprecations since January would constitute breaking v3 changes. Ultimately #10355 should resolve this, but it would be ideal for there to be tooling support for the first quarter following an API freeze to prevent these breaking changes.

@htuch
Copy link
Member Author

htuch commented Mar 13, 2020

Same for field renames as well, see #10325.

@htuch htuch self-assigned this Mar 22, 2020
@htuch htuch added help wanted Needs help! and removed help wanted Needs help! labels Mar 22, 2020
@htuch htuch removed their assignment Mar 22, 2020
@htuch htuch self-assigned this Apr 2, 2020
@htuch
Copy link
Member Author

htuch commented May 4, 2020

Since v3 is now the canonical API, this no longer applies.

@htuch htuch closed this as completed May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api/v3 Major version release @ end of Q3 2019 bug help wanted Needs help! priority/high
Projects
None yet
Development

No branches or pull requests

1 participant