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

Receiving Tracer on library construction #143

Closed
SergeyKanzhelev opened this issue Jun 20, 2019 · 2 comments
Closed

Receiving Tracer on library construction #143

SergeyKanzhelev opened this issue Jun 20, 2019 · 2 comments
Labels
area:api Cross language API specification issue
Milestone

Comments

@SergeyKanzhelev
Copy link
Member

see discussion: #135 (comment)

@SergeyKanzhelev SergeyKanzhelev added the area:api Cross language API specification issue label Jun 20, 2019
@SergeyKanzhelev SergeyKanzhelev added this to the API revision: 07-2019 milestone Jun 20, 2019
@SergeyKanzhelev SergeyKanzhelev removed this from the API revision: 07-2019 milestone Sep 27, 2019
@bogdandrutu bogdandrutu added this to the Alpha v0.3 milestone Sep 30, 2019
@tedsuo
Copy link
Contributor

tedsuo commented Dec 4, 2019

Closing this stub for now

@tedsuo tedsuo closed this as completed Dec 4, 2019
@jmacd
Copy link
Contributor

jmacd commented Dec 4, 2019

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
Labels
area:api Cross language API specification issue
Projects
None yet
Development

No branches or pull requests

5 participants