[DOC] high-level explanation of deprecation policy principles #6364
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
fkiraly
requested review from
achieveordie,
benHeid and
yarnabrina
as code owners
|
I just thought about deprecation while coding up PR #6373. This guide would have clearly answered my questions. |
|
Thanks for the positive feedback - that's why I was writing this! |
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.
This PR adds a preamble to the "deprecation policy" document in the developer guide, explaining why we need a deprecation policy, and high-level principles from which the policy elements are derived.
This should hopefully provide a better degree of illustration and explanation to new developers that we onboard.
A review by new developers (e.g., summer mentees) is especially welcome, as this is written for you.