Skip to content

api: introduce WiP file-level annotations.#9826

Closed
htuch wants to merge 1 commit intoenvoyproxy:masterfrom
htuch:status-annotations
Closed

api: introduce WiP file-level annotations.#9826
htuch wants to merge 1 commit intoenvoyproxy:masterfrom
htuch:status-annotations

Conversation

@htuch
Copy link
Copy Markdown
Member

@htuch htuch commented Jan 24, 2020

This is the new style for indicating a file is WiP and subject to
breaking changes. Rather than rely on alpha major versions, which are
coarse grained and introduce migration difficulties for operators, we
use a file-level annotation.

Risk level: Low
Testing: API/docs build, manual inspection of docs.

Fixes #9769.

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

This is the new style for indicating a file is WiP and subject to
breaking changes. Rather than rely on alpha major versions, which are
coarse grained and introduce migration difficulties for operators, we
use a file-level annotation.

Risk level: Low
Testing: API/docs build, manual inspection of docs.

Fixes envoyproxy#9769.

Signed-off-by: Harvey Tuch <htuch@google.com>
@repokitteh-read-only
Copy link
Copy Markdown

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

🐱

Caused by: #9826 was opened by htuch.

see: more, trace.

@htuch htuch requested review from lizan and mattklein123 January 24, 2020 21:04
@htuch htuch assigned lizan, markdroth and mattklein123 and unassigned markdroth Jan 24, 2020
@htuch
Copy link
Copy Markdown
Member Author

htuch commented Jan 24, 2020

CC @markdroth @dfawley @ejona86 FYI, hopefully not too controversial given that we agreed that well telegraphed API instability is OK.

@dfawley
Copy link
Copy Markdown
Member

dfawley commented Jan 24, 2020

FYI, hopefully not too controversial given that we agreed that well telegraphed API instability is OK.

SGTM, thank you for the heads-up.

Copy link
Copy Markdown
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!

@stale
Copy link
Copy Markdown

stale Bot commented Jan 31, 2020

This pull request has been automatically marked as stale because it has not had activity in the last 7 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

@stale stale Bot added the stale stalebot believes this issue/PR has not been touched recently label Jan 31, 2020
Copy link
Copy Markdown
Contributor

@markdroth markdroth left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks!

@stale stale Bot removed the stale stalebot believes this issue/PR has not been touched recently label Feb 3, 2020
Copy link
Copy Markdown
Member

@lizan lizan left a comment

Choose a reason for hiding this comment

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

Was revisiting this for new extension, and found (1) in #9769 (comment) doesn't have much tooling complex if we use move_to_package. So I guess we can continue to use vNalpha, WDYT @htuch?

option java_outer_classname = "TapProto";
option java_multiple_files = true;
option (udpa.annotations.file_migrate).move_to_package =
"envoy.extensions.transport_sockets.tap.v3";
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We can use this annotation altogether with the status, we can easily achieve v3alpha package for files subject to breaking change.

@mattklein123
Copy link
Copy Markdown
Member

@lizan is going to take over this change so I'm going to close this out and he can open a new PR. Thank you!

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.

Support vNalpha in protoxform and API boosting

5 participants