/
DEPR Meetings Notes (2025)

DEPR Meetings Notes (2025)

 

DEPR Project board

 

Nov 13, 2025

  • Board review starting from the Draft column

Oct 30, 2025

  • [Peter] progress page updates

  • [Peter] what is going on with forums?

  • [Peter] ProctorTrack deprecation ongoing

    • some more cleanup out of platform code

  • [Deborah] Program dash

    • no deprecation ticket exists yet

    • can make a fast track deprecation ticket for this

  • [Robert] Process improvement

    • Board review?

      • When we set the review after date set further in the future

      •  

Oct 10, 2025

  • Process updates as organizations move off deploying off master

    • Focused on release rather than dates

    • We want to keep a lot of the same processes in general, but we can be looser on specific dates.

      • Developers still will develop against master

        • need to make sure that developers are prepared when breaking changes land

    • Breaking changes don’t always get into the release notes

  • 2U has gone through the work to fork several repos so we can get on the named release schedule

    • forked edx-platform and credentials, as well as all the MFEs

  • @Maria Fernanda Magallanes Z I have a question regarding the DEPR process

    • https://github.com/openedx/edx-platform/issues/37409

    • What should the next steps be, or is it okay to just notify the community that we are going to make that change with that depr issue? (Ulmo cut)

      • Since the changes for Ulmo are not breaking for the current functionality, it shouldn’t be a problem to land it in Ulmo.

      • Announcement will still go out ASAP, but breaking changes are planned to land for Verawood, so this will match our existing expand-contract model.

  • Project Proposal

    • https://openedx.atlassian.net/wiki/spaces/OEPM/pages/5269422110

    • Move legacy program dashboard to learner dashboard so it’s a 1-to-1 replacement.

    • Work is going smoothly.

    • Aim for the new dashboard to be available in Verawood and the legacy code in edx-platform to be removed in the W release

      • Add a waffle flag to toggle which one is used.

      • Use the new one by default.

Oct 2, 2025

  • 2U switching to named releases with Ulmo

    • (for MFEs and edx-platform)

    • We can’t really change the deprecation process until all of our services are off of deploying off of master/main.

    • MIT will remain following close to master for now

  • Can we handle expand/contract migrations/settings between release boundaries?

    • We already are doing some of this.

  • What’s the future of production.py and the yaml settings file?

    • YAML will go away

    • Operators will be expected to maintain their own settings file (many are doing this anyway) and then import it/use DJANGO_SETTINGS env variable to set it.

  • What’s the status of the proctor track deprecation?

 

Sep 4, 2025

Aug 21, 2025

Announcing the Frontend-base Release Strategy Summit: https://openedx.atlassian.net/wiki/spaces/COMM/pages/5178359809

Aug 7, 2025

General Frontend DEPRs:

  • https://github.com/openedx/public-engineering/issues/416

    • Slots are still gonna be there but the configuration and names are changing so operators will need to update their configuration.

    • Will the transition still work in three years?

      • Will you be able to re-build your tutor MFE images in 3-years time?

        • Already a problem with NPM dependencies mismatching over that time period.

        • We pin dependencies but far enough in the future, transitive dependencies get upgrade in an unexpected way.

    • How difficult would it be to have a shim for configration V1 and V2?

      • For all of it, it would be pretty difficult but we could do it for the slot names.

    • In Ulmo, have a new branch in all the MFE repo called Next. Changes not merged to master by Ulmo, but landed in next

      • How do operators try out next?

        • There is a branch of tutor MFE that defaults to next

        • There are a lot of details to still work out.

  • https://github.com/openedx/public-engineering/issues/413

    • Mostly things can be dropped in via slots instead.

    • The big exception is probably going to be segment.

      • We need to generalize the eventing to make it possible to drop the direct dependency.

        • Ideally this would be a group effort to pair together and come up with a solution.

  • https://github.com/openedx/public-engineering/issues/414

    • Making this official though we haven’t see these in the code in a while.

  • https://github.com/openedx/public-engineering/issues/415

    • There are many alternatives to this for the different ways we’ve been using this. In the future you’ll control your index.html and can just make the modifications you want.

MFE-specific DEPRs:

An ADR proposing a new “next” branch for frontend repos that is not subject to the DEPR process that currently exists (it will still be subject to a DEPR process, but indirectly):

  • https://github.com/openedx/frontend-base/pull/94/files

  • Why so many DEPRs?

    • Coming out of the Frontend-base refactor

  • New Plan

    • Early tag things for Ulmo so we can land frontend-base stuff to master.

    • If people want more time to land things in ulmo MFEs they’ll have to backport to the ulmo branches.

24 July 2025

  • Proposed DEPR:

    • deprecate master branch, starting with frontend repos

      • context: https://github.com/openedx/frontend-app-authn/issues/1498

      • mostly edx.org/2U features

      • create next branch as an effective master branch

      • new features developed against next, backported to master

      • expected that people don’t run on master eventually, not considered stable and production-ready

        • This is the main focus of the deprecation

        • We will need to define what it means to ‘support’ production on the master branch

      • will try to move to this for all repos

  • This is kind a backdoor discussion of a bunch of deprecations in the frontend-build refactoring

    • Each feature will have its own DEPR tickets

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