2026-06-01 BTR Meeting notes

Follow-up Jun 1, 2026

Testing

• Sandbox testing - How is it going? Has the community started joining in?

• Blockers - Any issues found so far that could affect the June 23rd date?

Board cleanup

• Spring cleaning - How is the bug triager cleanup going? Any progress on moving/closing issues?

Release date

• June 23rd - still maintains given our last conversation, but we should check in on any potential blockers that could affect this.

No blockers reported by anyone. Chelsea noted she still needs to go through the bug board and will flag any release blockers once she does, but as of the meeting nothing was identified that could affect June 23rd.

June 23rd Confirmed and still on track. Peter asked to double-check the date and María confirmed it. The group acknowledged there are only 22 days left from June 1st, but no one raised a blocker against it.

Check per role

Group Chair

• Any coordination needed heading into the testing phase?

Release Manager @Farhaan Bukhsh

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

• Is the new release cadence proposal written up?

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 spring cleaning going?

Security Patcher

• Any security items to flag for Verawood?

1. Testing process - @María de los Ángeles Aguilar Testing is in progress. Current progress: General tests tab 0.2%, Frontend tests tab 0.0%, RBAC tests tab 36.4% completed.

2. Product Liaison - @Chelsea Rathbun: Two Testathons are scheduled: tomorrow June 2nd at 10:00 a.m. EDT Link to the June 2nd event invite. and Wednesday June 10th at 10:30 a.m. Link to the June 10th event invite. Chelsea also claimed a block of tests to complete on her own. Regarding the bug board, she will review it today or tomorrow to identify potential release blockers. Additionally, when reaching out to teams about testing, she already shared the release notes wiki to help kick off that process early.

3. Release Documentation Expert - @Chris Patti: It's early, but anything we can do to support documentation now? Action taken: Chris will check this week whether release notes are in place on the corresponding wiki page, beat the drum with teams to start adding the raw material needed. Confirmed the release date is approaching and it's time to formally kick off the documentation process.

4. Bug Triagers - @Mariagabriela Giorgianni @Bryann Valderrama @Kevyn Suarez@Deimer Morales The team is actively working on the board spring cleaning, triaging issues throughout this week. Maga left a message in Slack requesting Chelsea's help with some board items and confirmed she will address it today or tomorrow.

Additional topic

@Peter Pinch Brought a proposal from the conference: there is interest from several community members Jesse Smith, Ryan from WGU, Max from Raccoon Gang) in building automated end-to-end tests using Playwright. The proposal is to create a separate new repository for these tests rather than adding them to existing repos, to avoid slowing down the current process. Peter will check with Serena on how to create a repo in Open edX and will try to invite Jesse and Ryan to the next meeting to coordinate further details.