2025-03-31 BTR Meeting notes

Last Meeting Follow Up

@Maria Grimaldi

• 2025-03-17 BTR Meeting Minutes

• @Chris Patti follow up with Peter about code annotations tooling and conventional commits concern.

• @Chelsea Rathbun will assist with the cleanup testing sheets.

  • Confirmed that cleaning up the testing sheet is still on her to-do list.

• @Maria Grimaldi followed up with Edly for coordination on the testing environment: Teak Sandbox and Release Preparation

  • The issue for the testing environment has been created, following the same dynamic as the last release.

• Teak Release Preparation: sandbox ✅, testing sheet?, roles?

• Release Blockers: Build-Test-Release Working Group • openedx

Libraries support for units is at risk due to tight timelines. It’s a key Teak feature and potential blocker. Current estimates show delivery between April 15–25. Can we discuss next steps and timeline impact?

@Jenna Makowski

Content Libraries Project & Possible Release Delay

• Jenna explained that the content libraries project is expected to be ready between April 15–25.

• This timeline would miss the current Teak code cut.

• There is support in the group for pushing the code cut back by 1–2 weeks to include this work.

• Jorge noted this would still provide the usual six weeks for testing.

• Chelsea added that Axim is planning in-person user-facing testing during the week of April 28.

Next Steps on Release Date

• The group agreed to continue the discussion on Slack.

• A final decision is expected during the Thursday planning session (Maria won’t attend, Jorge will).

• The new tentative code cut target is the last week of April.

Roles for Teak

Status of Roles

• Roles post: 🚨 Call for Help: 🚀 Join the BTR Working Group for the Teak Release and Beyond! 🚀

• We still need a Release Testing Coordinator and Security Patcher

• No testing coordinator or security patcher has been confirmed.

• Maria spoke with Andres, who cannot take on the testing coordinator role this release.

• Maria posted a call for volunteers, but responses have been limited.

• Maria confirmed participation from four bug triggers and confirmation for roles filled by Farhan, Chelsea, Chris, and herself.

Fulfilling Key Roles

• Maria will repost and share the request for a testing coordinator in other working group channels.

• Suggestions were made to clarify the responsibilities and emphasize that the role is non-technical and supported.

• Jorge suggested reaching out to the security working group for help finding a security patcher.

• Maria may ask Maga for help finding someone from that group.

Go/No-Go Meeting?

• Do we need a Go/No-Go meeting? Depends on previous items.

  • Will confirm in planning meeting whether the code cut was pushed up.

Maintainers' responsibilities

Maintainers' Role in Release Notes

2025-03-06 Meeting notes | \uD83D\uDDE3 Discussion topics

• The idea of maintainers contributing more actively to release notes (operator and developer) was raised again.

• Maria will revisit this topic and consider updating documentation or writing an ADR (e.g., OEP-55).

Before the Teak branch cut, are we aligned on using release/teak instead of open-release/teak.master?

• Forum thread

• ✅ Release manager in the loop.
  
  

Release & Planning Meeting Schedule

• The meeting schedule should be updated after the code branch is cut.

• Agreement to wait until after Thursday’s meeting to finalize this.

• Once BTR meetings switch to weekly, community release planning sessions might be reduced to avoid meeting overload.