Milestones proposal (clarification) #152
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SergeyKanzhelev
requested review from
AloisReitbauer,
bogdandrutu,
c24t,
carlosalberto,
iredelmeier,
reyang,
songy23,
tedsuo and
yurishkuro
as code owners
SergeyKanzhelev
changed the title
songy23
approved these changes
Jun 21, 2019
bogdandrutu
reviewed
Jun 21, 2019
bogdandrutu
approved these changes
Jun 21, 2019
reyang
reviewed
Jun 21, 2019
milestones.md
Outdated
| Milestones for Java and cross-language specification: | ||
|
|
||
| - End of June: | ||
| - basic SDK implemented in Java. |
There was a problem hiding this comment.
Does "basic SDK" include support for logs?
reyang
reviewed
Jun 21, 2019
reyang
reviewed
Jun 21, 2019
| - Mid September (or after end-user validation): | ||
| - API is revised | ||
| - End of September (or after end-user validation): | ||
| - Version 1.0 is declared. |
There was a problem hiding this comment.
It's unclear that whether 1.0 will support logs or not.
There was a problem hiding this comment.
If 1.0 doesn't cover logs, do we introduce logs in v2.0?
There was a problem hiding this comment.
We can introduce in 1.5 (random minor version) as long as we don't break compatibility.
There was a problem hiding this comment.
If library A is using v1.0 opentelemetry-api, application B uses library A and v1.5 opentelemetry-sdk, build would fail since the SDK cannot find the corresponding logging methods defined in the API package.
Technically this is solvable, we can discuss later.
There was a problem hiding this comment.
Not sure what language (linker) you are referring to. The way to resolve this is application B will enforce api & sdk with the same version (1.5) and the library A will happily use that because of backwards compatibility.
reyang
approved these changes
Jun 21, 2019
SergeyKanzhelev
added a commit
to SergeyKanzhelev/opentelemetry-specification
that referenced
this pull request
Feb 18, 2020
* milestones proposal * adjustments * added TLDR * missing semicolons * Update milestones.md * Update milestones.md * added links to the milestones
TuckTuckFloof
pushed a commit
to TuckTuckFloof/opentelemetry-specification
that referenced
this pull request
Oct 15, 2020
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 21, 2024
Resolves open-telemetry#1324 I believe changes to semantic conventions and the shape of emitted telemetry are likely to occur during the lifetime of an instrumentation library. I do not think we should aim to lock the telemetry schema and disallow changes to it. Such locking would place a huge limitation on how instrumentation can evolve and would make it nearly impossible to fix mistakes in the semantic conventions, in the schema or in the implementation of the instrumentation (which will inevitably happen sooner or later). This OTEP introduces the concept of telemetry schemas that allows semantic conventions and instrumentations to evolve over time without breaking consumers of telemetry.
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 23, 2024
Resolves open-telemetry#1324 I believe changes to semantic conventions and the shape of emitted telemetry are likely to occur during the lifetime of an instrumentation library. I do not think we should aim to lock the telemetry schema and disallow changes to it. Such locking would place a huge limitation on how instrumentation can evolve and would make it nearly impossible to fix mistakes in the semantic conventions, in the schema or in the implementation of the instrumentation (which will inevitably happen sooner or later). This OTEP introduces the concept of telemetry schemas that allows semantic conventions and instrumentations to evolve over time without breaking consumers of telemetry.
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 31, 2024
* milestones proposal * adjustments * added TLDR * missing semicolons * Update milestones.md * Update milestones.md * added links to the milestones
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This proposal clarifies milestones of API revisions and SDK implementation. We are still shooting for a stable version of all project components in September and Sunset in November.
Milestones are quite aggressive to fit the desired goal.