-
Notifications
You must be signed in to change notification settings - Fork 893
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
Versioning and Stability for OpenTelemetry #1291
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the heroic effort to define this @tedsuo! My comments are only "issues", but in general this a huge step for the community and I'm really glad to see it happen.
My comments are mostly things I think we should open issues for and resolve via separate discussions, but just wanted to check to see if others agree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Thanks! A couple of small clarifications, but this generally is excellent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ted, thanks a lot for leading this!
@@ -62,7 +62,7 @@ The mechanism by which end users set or register a custom error handler should f | |||
### Examples | |||
|
|||
These are examples of how end users might register custom error handlers. | |||
Examples are for illustration purposes only. Language library authors | |||
Examples are for illustration purposes only. OpenTelemetry client authors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we discuss this renaming and make a decision on this? I am not against the change but it seems to me it is not a clear improvement over previous wording ("client" can be a confusing term).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, no group decision here. I began using the term "OpenTelemetry client" because "language library" wasn't clear - we have many libraries in each language, and none of these libraries contain a language. "Client" is a more common term for the set of components we are referring too. Open to other options.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't been able to elicit much comment on this one. There's some preference for "OpenTelemetry client" over "language library" as it is a more standard term 🤷♀️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is "OpenTelemetry client" different from "OpenTelemetry SDK", which is what we generally use?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yurishkuro OpenTelemetry client replaces "language library." It contains: API, SDK, SemConv, and Contrib.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
i put in minor suggestions for changes to fix grammar and make things more clear, but they are not blockers in my mind
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thank you everyone for all of the input. @open-telemetry/technical-committee can I get a merge? I believe this is complete for now. Future work:
|
@tedsuo Thanks! Will merge now as all comments are resolved and we have had enough approvals for some days now. Would you mind the issues for anything that is still needed? If there's still no issue for that, that is (as we have at least one issue regarding telemetry data already, etc). |
* Versioning and support based on OTEP 143
Changes
Related issues
Related OTEPS