Move messaging semconv stability SIG to "currently inactive" status#2683
Merged
trask merged 2 commits intoopen-telemetry:mainfrom Apr 21, 2025
Merged
Move messaging semconv stability SIG to "currently inactive" status#2683trask merged 2 commits intoopen-telemetry:mainfrom
trask merged 2 commits intoopen-telemetry:mainfrom
Conversation
trask
requested review from
alolita,
austinlparker,
danielgblanco,
jpkrohling,
mtwo,
mx-psi,
svrnm and
tedsuo
as code owners
arminru
approved these changes
Apr 17, 2025
mx-psi
approved these changes
Apr 21, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 put the messaging semconv stability SIG on hold at the beginning of March to focus on wrapping up Database semconv stability.
I discussed this week with @lmolkova and we are planning to focus our efforts on RPC semconv stability once Database semconv is marked stable at the end of this month.
Unfortunately, I don't think that leaves bandwidth for the messaging semconv stability SIG at this time, so I think better to officially move it to inactive status and attempt to reboot it once RPC semconv is stable.