docs: introduce DEPR pilot into OEP #660
Open
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
Add some more thoughts and we'll come back with more edits in the next meeting.
|
@robrap we made some more changes but there is still more to do, we'll continue to work on it at the next DEPR meeting but we will all try to review/add to what is here in the meantime. |
|
[Feel free to add to this TODO list if you aren't ready to make the updates.]
|
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 is to introduce the results of a successful pilot of some DEPR change into the DEPR OEP:
This was mostly around updated recommendations around DEPR timelines. The pilot was not perfect, and this update does not mean we can't iterate and improve.
Additionally, the pilot did not come up with a great way to determine when-and-if to DEPR, so separate follow-up will be needed for that.