2026-03-23 BTR Meeting notes

Follow-up from Last Meeting

Release process discussion

• Shared context from release planning meeting and raised questions about point releases and feature inclusion

• Discussed tradeoff between smaller frequent releases and need for impactful features to drive adoption

Backporting strategy

• Aligned that bug fixes and security patches should always be backported

• Identified open question around feature backporting, especially size and risk of features

Proposal next steps

• Agreed to move forward with a proposal document to define the release process more clearly

• Decided to collaborate on a shared document and review it with the broader group

• Next step is to draft the proposal and aim to review it in upcoming meetings

Process improvements

• Highlighted need for more visibility during development and better checkpoints for large features

• Noted issues with delayed testing environments and agreed to prepare earlier for next cycle

Roles and coordination

• Plan to define roles for upcoming release and share call for participation

Proposal for Verawood cut

Sarina’s proposal:

My proposal is that we shift both cut and release dates by two weeks. This would give us more time post-conference for Axim reviewers to finalize review and merge of high priority bugs. I think if we try to keep the release date June 9, realistically that date will be shifting anyway due to all the vacation planned.

https://discuss.openedx.org/t/proposal-shift-verawood-timeline-to-23-04-2026-cut-23-06-2026-release/18605?u=mgmdi

Roles for Verawood

https://discuss.openedx.org/t/call-for-help-join-the-btr-working-group-for-the-verawood-release-and-beyond/18569?u=mgmdi

Two Q’s:

1. How much time is required?

2. What role do we suggest for newcomers to take? Or shadow