Clarify that symbolic guarantees go into effect from 1.0.0 #467
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
We merged the open-telemetry#432 without clarifying when exactly the guarantees start applying. The intent was that the guarantees are needed for 1.0 release but we didn't make this explicit. We are now making this explicit and until 1.0 released we should be free to fix the remaining known issues listed here: open-telemetry#456 Once 1.0 release is made we can remove the [from 1.0.0] labels from the README.md.
This was referenced May 8, 2023
jsuereth
approved these changes
May 8, 2023
mx-psi
approved these changes
May 8, 2023
arminru
approved these changes
May 9, 2023
carlosalberto
approved these changes
May 9, 2023
dyladan
approved these changes
May 9, 2023
|
@open-telemetry/specs-approvers this has enough approvals. I will merge tomorrow if I do not see objections. |
bogdandrutu
approved these changes
May 9, 2023
VinozzZ
pushed a commit
to VinozzZ/opentelemetry-proto
that referenced
this pull request
Jun 21, 2024
…metry#467) We merged the open-telemetry#432 without clarifying when exactly the guarantees start applying. The intent was that the guarantees are needed for 1.0 release but we didn't make this explicit. We are now making this explicit and until 1.0 released we should be free to fix the remaining known issues listed here: open-telemetry#456 Once 1.0 release is made we can remove the [from 1.0.0] labels from the README.md.
VinozzZ
pushed a commit
to VinozzZ/opentelemetry-proto
that referenced
this pull request
Jun 21, 2024
…metry#467) We merged the open-telemetry#432 without clarifying when exactly the guarantees start applying. The intent was that the guarantees are needed for 1.0 release but we didn't make this explicit. We are now making this explicit and until 1.0 released we should be free to fix the remaining known issues listed here: open-telemetry#456 Once 1.0 release is made we can remove the [from 1.0.0] labels from the README.md.
VinozzZ
pushed a commit
to VinozzZ/opentelemetry-proto
that referenced
this pull request
Jun 21, 2024
…metry#467) We merged the open-telemetry#432 without clarifying when exactly the guarantees start applying. The intent was that the guarantees are needed for 1.0 release but we didn't make this explicit. We are now making this explicit and until 1.0 released we should be free to fix the remaining known issues listed here: open-telemetry#456 Once 1.0 release is made we can remove the [from 1.0.0] labels from the README.md.
VinozzZ
pushed a commit
to VinozzZ/opentelemetry-proto
that referenced
this pull request
Jun 21, 2024
…metry#467) We merged the open-telemetry#432 without clarifying when exactly the guarantees start applying. The intent was that the guarantees are needed for 1.0 release but we didn't make this explicit. We are now making this explicit and until 1.0 released we should be free to fix the remaining known issues listed here: open-telemetry#456 Once 1.0 release is made we can remove the [from 1.0.0] labels from the README.md.
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.
We merged the #432 without clarifying when exactly the guarantees start applying. The intent was that the guarantees are needed for 1.0 release but we didn't make this explicit.
We are now making this explicit and until 1.0 released we should be free to fix the remaining known issues listed here:
#456
Once 1.0 release is made we can remove the [from 1.0.0] labels from the README.md.