[chore] Use document status link to otel.io instead of versioned spec #1093
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
lmolkova
changed the title
reyang
approved these changes
May 29, 2024
3 tasks
ChrsMark
approved these changes
Jun 3, 2024
mx-psi
approved these changes
Jun 3, 2024
joaopgrassi
approved these changes
Jun 3, 2024
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.
Document status links are included in almost every doc and point to the latest version of the otel spec.
They create some noise in release PRs and are frequently out of date - see #1087 (comment)
This PR uses link on otel.io that points to the latest stable spec anyway, reducing the noise for semconv repo.