DEPR Project board

Aug 6, 2026

• From the Named Release Planning WG:

  • Will Mongo forums be deprecated in Willow?

  • What’s the status of the Library v1 deprecation?

  • React 18 upgrade? is it just waiting on legacy front-end DEPRs?

Jul 23, 2026

• Reviewed the board and made sure we had checked in on newer tickets that don’t have dates yet.

Jul 9, 2026

• Reviewed board and the few tickets up for review this time around.

Jun 25, 2026

• What’s the status of the removal of v1 libraries?

  • Removing the ability to create or edit new v1 libraries

• What’s the status of the instructor dashboard?

  • New dashboard doesn’t support the CCX dashboard yet

  • GWU is handling the work, but they’re focusing on their ulmo upgrade first

  • We don’t have a ticket for this work yet?

    • Actually, we do: https://github.com/openedx/openedx-platform/issues/38432

Jun 11, 2026

• Plugin slot issue was made backwards compatible in the meantime.

• Discussed whether we need to reschedule this meeting again.

  • Might need to bring this up on Slack to get more feedback.

  • Currently going to try Thursdays at 3pm EST and see if that works.

• Legacy studio templates and legacy libraries will also be removed in Willow

• Instructor dashboard deprecation

  • https://github.com/openedx/openedx-platform/issues/37214

  • What is the status of this work?

    • Most of the work has landed

    • CCX compatibility not there yet

• Modernization effort

  • pip-tools being replaced by uv

  • https://github.com/openedx/openedx-platform/issues/37053

    • This replacement should be in place now. Just need to ensure operators are prepared to update.

    • Should be happening for Willow

Apr 16, 2026

• toggles disappearing between Ulmo and Ulmo.1

  • This seems to be a discussions toggle that got removed(?)

  • This might be a security issue with permissions being too lenient

  • Maybe one of these commits?

    • https://github.com/openedx/openedx-platform/commit/fcfa4138fd02777505550e9ff2e86addda53072c

    • https://github.com/openedx/openedx-platform/commit/e64d4cee8db4d9c0f0a2067e8781590b76a39da8

• I think this PR that changed Plugin Slot names should have had a DEPR: https://github.com/openedx/frontend-app-learning/pull/1885

  • No DEPR was made (though it does have an ADR).

    • This was a breaking change, causing a feature targeting a slot to break.

    • The name of the slot changed, breaking code that uses the slot.

    • It was understood that slot names should be treated like APIs.

  • Was this introduced over the release boundary?

  • Will be brought up with the Frontend Working Group so that we can make sure the process is followed.

Mar 19, 2026

• Deborah made a discourse post asking for new maintainers for the enterprise repos

  • license-manager has a taker

  • After Mar 26, 2026 Deborah will open DEPR tickets for any with no takers.

Feb 19, 2026

• Should we have a separate Abandoned status from Rejected?

  • This would make it easier to move tickets that have been sitting in Draft for a long time into Abandoned.

  • Distinction:

    • Abandonded: we don’t want to put more resources or attention into doing something, but we don’t want to stop anyone from picking it back up

    • Rejected: this was an active decision to not decide to move forward on something

    • Draft(with help wanted tag): this seems small enough for someone to pick up, but no one is actively working on

  • Next steps:

    • update the OEP with information above

      • ensure that comments in the tickets clearly indicate the reasoning behind ending up in those states

    • publicizing the different statuses

  • Action items:

    Deborah will speak to 2U enterprise teams about making DEPR tickets (for example: https://github.com/openedx/edx-enterprise/issues/2467 )

    Robert will make a PR for Abandoned/Rejected split

Feb 5, 2026

• Review draft column

  • Do we to put dates on things?

    • By default, we will set things to 6 months for periodic review. Other tickets might have different dates depending on what we decide during review.

    • Dates may be useful in specific cases, and then we’ll use them.

  • What is our criteria for closing tickets or putting things in Reject/Abandoned?

    • Plans have changed since the tickets were created.

  • What about tickets that are semi-abandoned but we still want to do?

    • Can we use our time to help craft better/clearer tickets out of these?

    • Add a label/tag for “help-wanted” to help us track these.

      • Things that are well-written and ready.

• Quick Question(s) about https://github.com/openedx/public-engineering/issues/316

  • Product team seems to think this is still an open question (i.e. Verawood “Decision: Keep or lose horizontal nav” – but given this DEPR, I think that decision has been made, to lose the horizontal nav?

  • There is a post-closure question on the DEPR issue: https://github.com/openedx/public-engineering/issues/316#issuecomment-3114152505 “does the scope of this task also include removal of those legacy waffle flags from edx-platform? A quick search indicates that they are still present.”

  • Answer: This is already unsupported in the Learning MFE, but the waffle flags are still lingering in openedx-platform. Asking AXIM to help finish cleaning that up.

Jan 22, 2026

• How to handle the repos that are being transferred in ownership

  • 2U can’t maintain some repos anymore (mostly enterprise related) and we need to make tickets for those repos.

  • 2U is trying internally to get a list of repos from former owners, but this process has been slow going.

• Legacy Libraries ticket being rewritten

  • Verawood will be the last release to support legacy libraries

    • Might have impacts on any instance still running off master (like MITx)

  • New ticket should have better migration information and a full migration plan

    • Mostly tying together a bunch of existing documentation

  • Ulmo has user-facing docs on this process already

• Do we consider Django Admin changes breaking changes?

  • Yes, even then

Jan 8, 2026

• Working on old Studio UI removal work.

• LMS UI removal tickets have been accepted.

  • Lots of unused pages that are not removed yet.

• Removing a temporary toggle that crosses a named release boundary.

  • Just needs a release note, but doesn’t need a full depr ticket.

• How are we tracking a decrease in the number of toggles?

  • We can count the number of annotated toggles.

  • New toggles might be pylint checked to ensure all new toggles are annotated.

  • 271 as of Teak

    • +2 between Sumac and Teak

  • Probably should check with Ulmo to see the delta.

• Draft column?

  • Dedicate a specific meeting to the draft column in the past