BTR 2026-06-22 Meeting notes
All public Working Group meetings follow the Recording Policy for Open edX Meetings
Date
Jun 22, 2026
Participants
@Maria Grimaldi
Goals
Discussion topics
Item | Notes |
|---|---|
Test completion |
|
Release blockers | https://github.com/orgs/openedx/projects/28/views/17 We still have 5 blockers open/pending, but we’re making progress on them:
All blockers should be re-reviewed so we 100% agree they’re still release blockers |
Process overview: VerawoodRelease Manager @Farhaan Bukhsh
Release Testing Coordinator @María de los Ángeles Aguilar
Product Liaison @Chelsea Rathbun
Release Documentation Expert @Chris Patti
Bug Triagers@Mariagabriela Giorgianni @Bryann Valderrama @Kevyn Suarez@Deimer Morales
Security Patcher
|
|
Go / No Go (as of today) |
|
E2E Testing | Repo: https://github.com/openedx/end-to-end-tests/pull/1 Maintainers: https://discuss.openedx.org/t/cc-rights-expansion-ty-hob/19118 https://discuss.openedx.org/t/cc-rights-expansion-max-sokolski/19119 https://discuss.openedx.org/t/cc-rights-expansion-jesse-stewart/19120 https://discuss.openedx.org/t/cc-rights-expansion-peter-pinch/19117 |
Verawood Release (Decisions & next steps)
Decision list for Verawood release:
We will not move forward with the Verawood release until the two previously agreed conditions are met:
Test completion is above 80%.
There are no remaining release blockers.
Current Status
The test completion condition is now met, since we are currently at 83.1%.
The release is still not ready to move forward because there are still 5 blockers open/pending.
Next Steps
We will keep treating this as a Go/No-Go process, instead of leaving the release as an open-ended delay.
The next meeting will be used as the next Go/No-Go checkpoint to confirm whether we are ready to move forward.
Until then, the focus should be on release-critical work only:
Retesting the merged fix for #574 on the Verawood sandbox.
Triaging #588 and #587.
Continuing the review for #585.
Confirming whether any blockers should be reclassified or if they really need to keep blocking the release.
The release scope is frozen from now on. No non-critical changes should be included unless BTR agrees they are needed for the release.