2026-05-04 BTR Meeting notes

Follow-up items from Apr 20, 2026

Verawood release

• Branch cut done Thursday April 30. release/verawood and ulmo.3 are out.

• Legal clearance (Axim) for Kiro agent (unblocked before the cut).

• Core 1.0 + Libraries blockers all landed (Kyle confirmed April 22).

• LTI fix (Feanil): decided to proceed and backport later.

• RBAC backports: we only have one backport pending, but probably should have more. No blockers, just fixes that need to be backported.

• Sandbox: Ahmed Khalid (edly) said servers would be set up today. Estimate: Tomorrow EOD or today.

• tutor-minio: no formal commitment from edunext for a maintainer. Short-term or long-term solution still needed.

Indigo

• Keep OFF by default. Chelsea, Sam, Brian, Marco, and Abdul all aligned. Lazy consensus reached.

Testathon (May 6 and May 12)

• Dates confirmed: May 6 (9:30-10:30 EDT) and May 12 (10:30-11:30 EDT).

• UPDATE: Upcoming Virtual Test-a-thons postponed... stay tuned!

Frontend MFE core contributors

• Forum thread not yet started.

Verawood.1 cut

Are we still aiming for Jun 23, 2026 (~6 weeks from now)?

Meeting cadence

Ask Axim: can we move to weekly meetings for the duration of release testing?

Verawood Process overview: Jun 23, 2026

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

   • Ongoing work

   • Red flags, risks, and concerns

   • Call for help

2. New features testing - @Chelsea Rathbun

   • 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@Deimer Morales

   • Ongoing work

   • Release blockers

   • Call for help

6. Security - Jawad Khan

   • Ongoing work

   • Red flags, risks, and concerns

   • Call for help