/
2025-11-25 BTR Meeting notes

2025-11-25 BTR Meeting notes

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

 Date

Nov 21, 2025

 Participants

  • @Maria Grimaldi

  • @Peter Pinch

  • @aamir ayub

  • @Sara Burns

  • @Mariagabriela Giorgianni

  • @María de los Ángeles Aguilar

  • @Farhaan Bukhsh

  • @Bryann Valderrama

  • @Kevyn Suarez

  • @Santiago Suarez

 Goals

  •  

 Discussion topics

Item

Presenter

Notes

Item

Presenter

Notes

⚠️ Ulmo.1 ~ 2025-12-09

 

How are we feeling for the Dec 12, 2025ulmo.1 cut? Is is realistic considering the current state of the testing? - we can go back to this at the end of the meeting, once we do a review of the current state of the release process!

Release blockers



Build-Test-Release Working Group • openedx

  • No release blockers as of today, not from product or technical POV. Can we do a quick review on the test failures to ensure we don’t have any possible blocker?

  • Were all issues prioritized?

Ulmo Process overview

  1. Testing process - @María de los Ángeles Aguilar

    • Ongoing work

    • Red flags, risks, and concerns

    • Call for help

  2. New features testing - @aamir ayub

    • Ongoing work

    • Red flags, risks, and concerns

    • Call for help

  3. Release management - @Farhaan Bukhsh

    • Ongoing work

    • Red flags, risks, and concerns

    • Call for help

  4. Release documentation - @Chris Patti

    • Ongoing work

    • Red flags, risks, and concerns

    • Call for help

  5. Debugging - @Mariagabriela Giorgianni @Bryann Valderrama @Kevyn Suarez

    • Ongoing work

    • Release blockers

    • Call for help

 

  1. Testing process: How is testing going? What are the stats for today?196 completed. and only 25 failed resulting in 20 GitHub issues being opened.

  2. New features testing: Did we unlock content libraries testing (RBAC)? What about discovery?

  3. Release management: any concern? Do we need help with backports?

  4. Release documentation: how are we doing? Do we need any support?

  5. Debugging: can we do a quick review on the issues that have been reported during the last week? Do we have any concerns? Please share here!

 Action items

  1. Keep encouraging testers to increase the test completion rate

    • There was significant progress (now at 41.1%). @María de los Ángeles Aguilar Continue motivating those who haven’t participated yet.

  2. Verify the email flag fix and test again

    • Add comments if any issues remain; share the relevant PR with testers.

  3. Document and review pending notification fixes

    • @Farhaan Bukhshand @aamir ayub are responsible for monitoring and follow-up.

    • @Farhaan Bukhsh will document the cron job for notifications.

  4. Prioritize open issues, especially the high-priority ones

    • @aamir ayub is reviewing the unprioritized issues and expects to assign or close them soon.

  5. Review and possibly consolidate RBAC test cases

    • There was discussion about reducing the number of cases, but decided to keep broad coverage since it's a new feature.

    • @Jenna Makowski will help push this testing forward.

  6. @Bryann Valderrama to review the issue [Test failure] <TC-00147>: Studio sub/section name edits don't update in live preview · Issue #37676 · openedx/edx-platform and dedicate time to other reported issues, seeking thorough solutions and reported issue has already been transferred to edx-platform

  7. @Mariagabriela Giorgianni reports issue where posts aren’t visible in teams, plans to reopen the PR if it fixes the problem, and will seek help/tag for review.

  8. @aamir ayub takes the lead on notification test cases and asks the team not to test until fixes are ready.

 Decisions

  • Test deadline remains December 12.

  • No severe release blockers identified at the moment (just minor issues and pending documentation/fixes).

  • Coverage for RBAC test cases will not be reduced at this time.

  • Email/notification and post testing will wait for fixes before general testing is allowed.

  • Collaborative async work remains open after the meeting.