Once the ticket is accepted, removal won’t happen until after Ulmo is cut in mid-October, 2025.
After acceptance, all future notifications around removal will only be posted to the GitHub issue, so be sure to watch that issue if you want further updates.
Hello @SergiiKalinchuk. Welcome and thank you. From a process perspective (OEP-21), most of the details will be added to the DEPR issue and this page will be a light wrapper that does the announcing of that ticket. Since you are proposing a deprecation in edx-platform, you would use https://github.com/openedx/edx-platform/issues, choose “New Issue”, and choose the DEPR template. Let me know if you have any questions.
@SergiiKalinchuk Could you please follow OEP-21 as Robert describes above, making an issue on the edx-platform repo with these details, and editing this post to be the brief announcement that is described within OEP-21’s “deprecation/removal template”? Thank you!
The DEPR Issue in Github is definitely where you want to capture all the details. If the template is imperfect, and you need a new subheader to capture additional details, you can do that. Or add them to a comment. But we want all the information to be on the ticket. Some people will never read this, because usually it just gets people to the ticket/issue.
Once the ticket is accepted, removal won’t happen until after Ulmo is cut in mid-October, 2025.
After acceptance, all future notifications around removal will only be posted to the GitHub issue, so be sure to watch that issue if you want further updates.