-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: introduce DEPR pilot into OEP #660
base: master
Are you sure you want to change the base?
Conversation
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.]
|
|
||
This approach would be most appropriate for features that can be left | ||
in place for an extended period before removal and where a transition | ||
to an alternative would require a moderate to large amount of | ||
effort. For more trivial deprecations, it may be appropriate to simply | ||
deprecate and remove within the same release cycle. | ||
|
||
TODO: UPDATE THIS AND ALL OTHER PLACES TO MENTION target month + named release. Check the DEPR issue template as well. And scan throught the rest of this DEPR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also include a link to the release schedule in the DEPR template.
Co-authored-by: Diana Huang <[email protected]>
@@ -209,28 +209,40 @@ considers the timing of the next `Open edX named release`_. | |||
periods will vary by the type and scope of the technical change. | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: Update/replace the image in this DEPR.
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.