Introduce additional attribute requirement levels #2601 #2607
Conversation
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
thompson-tomo
changed the title
github-actions
bot
added
enhancement
github-project-automation
bot
moved this to V1 - Stable Semantics
in Spec: Messaging Semantics
thompson-tomo
force-pushed
the
chore/#2601_IntroduceAdditionalRequirementLevels
branch
from
67f2f00 to
c1e6f46
Compare
thompson-tomo
changed the title
thompson-tomo
force-pushed
the
chore/#2601_IntroduceAdditionalRequirementLevels
branch
from
a240fa4 to
f43abc8
Compare
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.
Fixes #2601
Changes
This defines 2 new attribute requirement levels migrate & remove which is used in conjunction with deprecations. With this change we can now see which attributes should be removed and which ones are needing to be migrated.
Note this is also needed for potential code generation as we are needing a way to support side by side.
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist
[chore]