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

api: freeze of v2 API, cut v4alpha API. #10672

Merged
merged 4 commits into from
Apr 7, 2020

Conversation

htuch
Copy link
Member

@htuch htuch commented Apr 7, 2020

This patch performs a major version freeze and bump by modifying
package_version_status, using the tooling developed in #10636.
Specifically:

  • v2 APIs are frozen (except for where they are the latest in their
    package history and still active)
  • v3 APIs are transitioned to be active
  • Candidate v4alpha APIs are generated (not used by Envoy yet)

Fixes #10355

Risk level: medium (entire API's files are modified, visually verified
to ensure things look sane, all tests pass)
Testing: CI

Signed-off-by: Harvey Tuch htuch@google.com

This patch performs a major version freeze and bump by modifying
package_version_status, using the tooling developed in envoyproxy#10636.
Specifically:

* v2 APIs are frozen (except for where they are the latest in their
  package history and still active)
* v3 APIs are transitioned to be active
* Candidate v4alpha APIs are generated (not used by Envoy yet)

Fixes envoyproxy#10355

Risk level: medium (entire API's files are modified, visually verified
to ensure things look sane, all tests pass)
Testing: CI

Signed-off-by: Harvey Tuch <htuch@google.com>
@htuch htuch requested review from lizan and mattklein123 April 7, 2020 00:54
@repokitteh-read-only
Copy link

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to api/.

🐱

Caused by: #10672 was opened by htuch.

see: more, trace.

mattklein123
mattklein123 previously approved these changes Apr 7, 2020
Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, awesome work.

Per offline convo, this PR will not yield any user error if someone accidentally modifies the v2 API. The changes just won't forward propagate. @htuch and I agreed that we can snap 1.14.0 with this PR, but we should do a fast follow to have a CI check that makes sure that moving forward the only changes to v2 protos are comment/doc changes, and no actual API changes. This is mostly to avoid developer confusion. Thank you!

@repokitteh-read-only repokitteh-read-only bot removed the api label Apr 7, 2020
Signed-off-by: Harvey Tuch <htuch@google.com>
@repokitteh-read-only repokitteh-read-only bot removed the api label Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Freeze v2 API
3 participants