/
DEPR Meetings Notes (2025)

DEPR Meetings Notes (2025)

DEPR Project board

 

 

Future

 

26 June 2025

  • Cookie name change ticket was completed

  • Fast Track template being updated.

    • Automation not in place yet, but there are instructions on how to move it through the process in a fast track way.

  • Board review

    • Updated/checked in on tickets that needed to be reviewed.

12 June 2025

@Feanil Patel to announce new process to the community

  • [Robert] [proposal] I added a comment like the following to all DEPRs in the Accepted state: https://github.com/openedx/brand-openedx/issues/23#issuecomment-2919418180.

    • (If you have comments on the wording, let me know and I can adjust before commenting. I learned in the Maint WG meeting that this particular DEPR ticket has plans for moving forward, so I got a jump start before it was too late. (Copied from Slack message.))

  • [Robert] Using the ‘review after’ date to fields on DEPR tickets.

    • We can focus on reviewing the tickets with the date (or without a date) during meetings.

  • Process change

    • New names, new fields, etc

    • Should we announce out the changes to the process?

      • Feanil is going to do this

      • Want to let the community know what is going on so they can follow the new process

  • Maintenance working group - using DEPR to announce breaking changes?

    • Example of a breaking change that is not a DEPR: https://github.com/openedx/edx-platform/pull/36885

    • Proposing: a new, streamlined method of creating DEPR tickets that won’t require a full DEPR template and process for smaller breaking changes

      • if we run into something that has been miscategorized, we can just move it back into the full DEPR process

  • Proctortrack

    • Removal as a default installation is because we don’t want to tie Open edX to any particular proctoring provider

    • We might be able to bring the Proctortrack plugin into the openedx organization, but that will require a compatible license or for the owners to contribute under the CLA

      • Unclear if 2U has any ownership of the code and can contribute it

29 May 2025

  • [Robert] [inform] Abandoned/Rejected won’t auto-close, so it doesn’t move to Plan Completed (as a closed ticket). These will need to be updated manually.

  • [Robert] [question] When closing, we have “Last Release with Feature” to fill in on ticket. Is there anything else?

    • Answer: That’s it.

  • [Robert] [proposal] I plan to add a comment like the following to all DEPRs in the Accepted state: https://github.com/openedx/brand-openedx/issues/23#issuecomment-2919418180. If you have comments on the wording, let me know and I can adjust before commenting. I learned in the Maint WG meeting that this particular DEPR ticket has plans for moving forward, so I got a jump start before it was too late. (Copied from Slack message.)

@Robert Raposa Add comment to all Accepted DEPR tickets.
[Diana] New Relic has been removed as a base dependency, though it is still supported via edx-django-utils.

15 May 2025

  • Retros were completed in Maintenance WG meeting on 15-May.

    • Retro for the Studio waffle flip

    • Retro for pre-Teak late-stage breaking changes to MFEs (FooterSlot)

    • [inform] Decision: Let’s use our updated process and board to inform.

  • [Robert] DEPR board review and process improvements.

01 May 2025

01 April 2025

  • Axim can’t make this one

  • Check in on readiness of the codejail-service for the Teak release

20 March 2025

  • Programs dashboard

    • legacy page

    • no DEPR or MFE replacement

      • Might make sense to make it part of the learner dashboard MFE

    • the API can be improved to prepare it for MFE migration

  • Can be pushed through after the Studio Legacy frontends deprecation work

  • Codejail service will be coming up as soon as the replacement in a good place.

    • Will want to try to merge the repos into one, maybe as part of the deprecation

    • We can ask the maintainers about trying to do this work once the ‘official’ implementation is in a good place

    • Discussed possibility of releasing this as part of Teak

      • We aren’t sure. Is about to be dark launched on edx.org.

      • We will check in during next DEPR

    • 2U/Arch-BOM will write the DEPR as the team who is doing the bulk of the work to develop the new codejail-service, but they won’t own the ticket going forward.

6 March 2025

  • Kyle: Will probably have questions for 2U w.r.t. edx-proctoring-proctortrack deprecation.

    • Diana: Should make sure the owning team is aware (Cosmonauts)

  • Forums v2 work will start up again soon. SOW sent out this week. No breaking changes until after Teak cut.

  • Diana: Work starting on codejail service replacement, but no immediate plan to remove codejail itself.

    • Dave: Is there place to tune in to this work?

      • Diana: Mostly internal. You can follow the tickets and there’s a public repo.

    •  

20 February 2025

6 February 2025

23 January 2025

09 January 2025

  • New year, new us - Migrating everything to point to new page

    @Kyle McCormick - finish up tasks from https://openedx.atlassian.net/wiki/spaces/COMM/pages/3996745737

  • [Diana] Forums deprecation - when is removal of support for v1 forums planned to land in master? Sometime before Teak, but obviously, 2U needs more solid dates.

    • This seems to have the date of March 1 now

      • We’ll start deleting the parts of code that talk to the ruby forums service.

    • Bugs with the software should be filed with the new repo

    • Internal to 2U, Arbi-BOM will be doing most of the engineering, supported by the Infinity team with their domain expertise.

  • [Kyle] Paver deprecation is very close to being completed!

    • Hooray.

  • [Feanil] Updates to the DEPR OEP - https://github.com/openedx/open-edx-proposals/pull/660