2025-10-03 BTR Meeting notes

Follow-ups from 2025-09-29 meeting

• Get Node 14 upgrade PRs merged https://github.com/openedx/public-engineering/issues/407 03/10 status update:

  • Issues opened: 35

  • 24 of 35 closed

  • 11 issues remaining

  • Without linked PRs: 7, 1 in progress, 6 remaining

    • paragon: not linked PR but listed in issue cover letter http://github.com/openedx/paragon/pull/3687 , under review

    • frontend-lib-special-exams: no PR in progress

    • frontend-app-support-tools: no PR in progress

    • edx-enterprise: no PR in progress

    • frontend-app-enterprise-public-catalog: no PR in progress

    • frontend-app-learner-portal-enterprise: no PR in progress

    • frontend-app-publisher: no PR in progress

• Testing sheet setup: https://docs.google.com/spreadsheets/d/1-gEXI4IiAn5mdROGDMxNcFHAaZCRu3mxVLNDmTdJFI8

  • Already shared in shared in the call for testers post: https://discuss.openedx.org/t/ulmo-call-for-testers/17271

  • Is the test sheet prep complete?

• Ulmo Sandbox, in progress:

  • https://github.com/overhangio/tutor/issues/1281

• Code cut planned for Thu Oct 9, 2025

• Weekly status meeting starting on Oct 3, 2025

• Graded discussions not a blocker. XQueue, Meilisearch, and problem editor deprecation won’t land in Ulmo.

Release Blockers

• Any potential blocker from the release manager for the cut-off on Thursday, 9th?

• Any blocker from the community?

Named Release Planning (Biweekly) on Oct 2, 2025

Here’s a short recap by discussion items from the Oct 2 release planning call:

Going well (green):

1. Django 5.2 upgrade → almost done, final switch pending

2. LTI store → PR expected, good shape

3. MF conversion (catalog/about) → backend merged, just final review

4. Postgres tutor plugin → one PR left, active progress

5. Legacy libraries migration → in progress, no issues

6. Import API, backup & restore, subsection/section reuse → all done

7. Configuring XBlocks UI → first phase done, rest scheduled for later release

At risk / not going well (yellow/red)

1. Node 24 upgrade → yellow, PRs in progress, reviews needed

2. Notifications MVP → yellow, slowed by developer illness, Oct 9 at risk

3. Progress page MFE fixes → yellow, 3 PRs open, tight timeline

4. Roles & permissions → red, heavy workload, many PRs open, high risk

5. XQueue replacement → won’t make Oct 9, deferred to Ulmo.1

6. Graded discussions → stalled since spring, not expected in Ulmo

Recommendation (from the meeting, open for discussion)

Delay Ulmo code cut at least one week beyond Oct 9 to allow at-risk work to land and stabilize.

Oct 9, 2025 cut Go/No go?

• Given this recap, do we feel ready for the Thu Oct 9 Ulmo cut?

• Go / No-go decision → what’s the confidence level, and what would block a “go”?