-
Notifications
You must be signed in to change notification settings - Fork 888
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
Receiving Tracer on library construction #143
Comments
Closing this stub for now |
Please take this discussion to open-telemetry/oteps#45 |
TuckTuckFloof
pushed a commit
to TuckTuckFloof/opentelemetry-specification
that referenced
this issue
Oct 15, 2020
rockb1017
pushed a commit
to rockb1017/opentelemetry-specification
that referenced
this issue
Nov 18, 2021
* Update instrumentation specification - Mostly refactoring of existing language. - Mark RUM and serverless experimental * Update CHANGELOG
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this issue
Oct 21, 2024
Link to readable version: https://github.com/tedsuo/rfcs/blob/versioning/text/0143-versioning-and-stability.md Versioning is a high priority as we still hope to get some kind of release or announcement out by end of year. This proposal explains the versioning protocol and stability guarantees for OpenTelemetry implementations in every language. It would be a helpful exercise to have maintainers review this proposal, and write out their language specific-expectations. **Request for Maintainers:** Please create a language-specific document which describes how versioning and support works for your language, based on this OTEP, and post a link to it in the [tracking issue here](open-telemetry#1267). We want to ensure that versioning and support as been thought through before it is added to the spec. Cheers, -T
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this issue
Oct 23, 2024
Link to readable version: https://github.com/tedsuo/rfcs/blob/versioning/text/0143-versioning-and-stability.md Versioning is a high priority as we still hope to get some kind of release or announcement out by end of year. This proposal explains the versioning protocol and stability guarantees for OpenTelemetry implementations in every language. It would be a helpful exercise to have maintainers review this proposal, and write out their language specific-expectations. **Request for Maintainers:** Please create a language-specific document which describes how versioning and support works for your language, based on this OTEP, and post a link to it in the [tracking issue here](open-telemetry#1267). We want to ensure that versioning and support as been thought through before it is added to the spec. Cheers, -T
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
see discussion: #135 (comment)
The text was updated successfully, but these errors were encountered: