2025-09-29 BTR Meeting notes

All public Working Group meetings follow the Recording Policy for Open edX Meetings

Date

Sep 29, 2025

Participants

@Maksim Sokolskiy
@Peter Pinch
@Jenna Makowski
@Sarina Canelake
@aamir ayub
@María de los Ángeles Aguilar
@Jorge Londoño

Goals

Reviewing the prep work for Ulmo release

Discussion topics

Item	Presenter	Notes

Item	Presenter	Notes
Recap From Last Meeting		Roles for the Ulmo Release: Ulmo Release Roles: https://discuss.openedx.org/t/call-for-help-join-the-btr-working-group-for-the-ulmo-release-and-beyond/16757 Group Chair: @Maria Grimaldi with Jorge’s help! Release Manager: @Farhaan Bukhsh Release Testing Coordinator → @María de los Ángeles Aguilar Release Documentation Expert: @Chris Patti Bug triager(s): @Bryann Valderrama @Kevyn Suarez @Mariagabriela Giorgianni Security Patcher → @Gábor Boros Product Liaison: @aamir ayub
Updates for Prepping Tasks for Ulmo		Release Testing Coordinator Follow-up - Peter & Maria Release Testing Coordinator & Product Liaison - Maria & Aamir Testing Sheet: https://docs.google.com/spreadsheets/d/1-gEXI4IiAn5mdROGDMxNcFHAaZCRu3mxVLNDmTdJFI8/ Product Liaison - Aamir: New Test Cases Release Manager - Farhaan Any blockers for cutting branches on Oct 9, 2025 Ulmo Sandbox @Ahmed KhalidWill Edly be able to help us get the sandbox environment ready for the testing process kick-off? Board Management: How are we doing? Release blockers: https://github.com/orgs/openedx/projects/28/views/17 - 1 blocker, addressed in next discussion item (node 24 upgrade) Release Documentation Sarina’s question in Slack: Hi all, who knows the release scripts well and could help me with a change? Specifically I would like to ensure that the `docs.openedx.org` repo does not get tagged for release during the code cut, but does get tagged at the final release. Otherwise I have to maintain a long list of backports as we get release notes written and pages updated. Like this one :\ https://github.com/openedx/docs.openedx.org/pull/1068
Release Planning 18/09		Node 24 upgrade: About 70% coverage so far (≈11 repos, ~3 PRs each: enable CI, add Node 24, remove Node 20). Many PRs are waiting for review and merge. Current Node version will be out of support before the next named release → marked as red, considered a blocker. Need CCs and maintainers to review and merge quickly; Feanil helping to accelerate. @Maksim Sokolskiy compiling full PR list, tracked under public engineering issue 407. Roles and permissions work still in progress, flagged as another area of concern. Graded discussions might be too late to include unless scope and resourcing are confirmed by early October. Legacy libraries migration and course-to-library import are moving, but timelines are tight. Meilisearch upgrade may not make it due to sequencing with other library migrations. XQueue replacement in development, still marked yellow; not expected to block. Legacy problem editor deprecation was raised late in the call. It’s not tracked on the sheet but could have architectural impact by reducing frontend code maintenance.
Proposal for Board Management		Testing Failures Board Maintenance Process [WIP]
Teak Retro Items

Action items

@Jorge Londoño - Reaching out to Farhaan to identify any potential blockers or help needed for the cut-off next week.

@Jorge Londoño - Posting a call for help for reviewing the PRs of https://github.com/openedx/public-engineering/issues/407

@María de los Ángeles Aguilar - Finalizing the set-up of the testing sheet.

@aamir ayub - Reaching out to Ahmed to get an update on the Ulmo sandbox set-up.

BTR - Reviewing and commenting on Testing Failures Board Maintenance Process [WIP]