Add placeholder for messaging stabiblity transition plan #734
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.
Fixes #720
Changes
Added the same warning as was added for database semantic conventions in #733.
I removed the warning about network attributes, as those are also part of database semantic conventions and don't merit a warning there. I'm not aware of any messaging instrumentation that has implemented the prescribed stability mechanisms for network attributes.
Merge requirement checklist
Change log entry added, according to the guidelines in When to add a changelog entry.[chore]
schema-next.yaml updated with changes to existing conventions.