BTR 2026-06-22 Meeting notes

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

Item

Notes

Test completion

  • We’re currently at 83.1%!!

  • According to NOT ASSIGNED & NOT STARTED views, here are the areas missing testing: https://docs.google.com/spreadsheets/d/1j1uDhVIVLwHUfrMLBzx6lM55gYL6i4nUqbzkbLHpaHQ/edit?gid=1705224758#gid=1705224758&fvid=610571984

    • LMS: COURSE HOME: TOOLS

      • Personal Note-Taking

    • PLUGIN: CREDENTIALS

      • Credentials – Verifiable Credentials Setup & Integration

    • STUDIO XBLOCKS

      • Course Authoring – Google Calendar XBlock Configuration

    • STUDIO: CONTENT: OUTLINE

      • “Learn more” help links in Studio point to the correct Verawood release documentation

    • STUDIO: SETTINGS: ADVANCED

      • Enable and Verify Mobile Course Availability in Advanced Settings

    • STUDIO LIBRARIES: Manage Team

      • Revoke a role from a library member
        / Deleting last role redirects to Team Members and removes user from the list

      • Allow reuse by all Studio users
        /Reuse toggle is visible to team managers and defaults to Off

      • Allow reuse by all Studio users
        /Turning reuse toggle On enables published content access for unaffiliated Studio users

    • LMS: Notifications Email

      • Delivery of Email notifications with Immediate cadence

      • Notifications are grouped by type and context in tray and email summaries

    • AUTHORING MFE: COURSE OUTLINE
      AUTHORING MFE: COURSE FILES

      • File Upload Agreement

    • AUTHORING MFE: COURSE OUTLINE
      AUTHORING MFE: COURSE VIDEO

      • Video Upload Agreement

      • File and Video Upload Agreement

    • LMS: INSTRUCTOR: COURSE TEAM

      • Course Team Management – Extended Role Assignment

    • LMS: INSTRUCTOR: GRADING

      • Course Grading – Single Learner Adjustments

    • LMS: INSTRUCTOR: DATE EXTENSIONS

      • Course Flexibility – Individual Deadline Management

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: Verawood

Release Manager @Farhaan Bukhsh

  • Was Ulmo .4 cut as planned? Any other point releases?

  • Do we have any backport to consider?

Release Testing Coordinator @María de los Ángeles Aguilar

  • How is testing going on the sandbox? How many people are participating?

  • Any issues or blockers found?

Product Liaison @Chelsea Rathbun

  • Any updates from the Product WG? Any features that still need tests written

Release Documentation Expert @Chris Patti

  • Any updates on release notes for Verawood?

Bug Triagers

@Mariagabriela Giorgianni @Bryann Valderrama @Kevyn Suarez@Deimer Morales

  • How is the board maintenance going?

Security Patcher

  • Any security items to flag for Verawood?

 

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.