Content Comparison

Newsfeed

Sumac retrospective

• Sumac.1 Retrospective 🌳⏪

Jorge Londoño

1. The async retrospective space is open for feedback, with two weeks to contribute before reviewing results in the next BTR meeting.

Retrospective action items follow-up

• https://github.com/openedx/wg-build-test-release/labels/retrospective

Jorge Londoño

1. Follow-ups on Redwood retrospective action items will continue asynchronously via GitHub issues.

Next release

• 2️⃣ sumac.2 ~ 2025-02-0910

  • Release blockers

  • Process overview

    • Testing process - Peter Pinch Andrés González

      • Ongoing work

      • Red flags, risks, and concerns

      • Call for help

    • New features testing - Chelsea Rathbun

      • Ongoing work

      • Red flags, risks, and concerns

      • Call for help

    • Release management - Farhaan Bukhsh

      • Ongoing work

      • Red flags, risks, and concerns

      • Call for help

    • Release documentation - Chris Patti

      • Ongoing work

      • Red flags, risks, and concerns

      • Call for help

    • Debugging - Maria Grimaldi

      • Ongoing work

      • Release blockers

      • Call for help
        

• 🌳 Teak

  • ✂️ teak.master ~ 2025-04-09

  • 1️⃣ teak.1~ 2025-06-09

  • The next Release Planning session is on Thursday 06/02.

Jorge Londoño

Sumac.2 Release (First Point Release of Sumac)

• Scheduled for Monday, Feb 10

• No blocking issues have been reported.

• Three high-priority bugs were identified:

  • Two seem to have easy fixes but need someone to work on them this week.

  • Expected to be resolved before the release cut.

  • Maria Grimaldi and Farhaan Bukhshoffered to help fix pending issues (or at least find someone on their teams to do it) before the release.

• Contributors are encouraged to assist in addressing the issues before the deadline.

• Backports and release notes were briefly discussed; no major concerns were raised.

Sumac.2 Operational Readiness

• Farhaan Bukhsh confirmed readiness for the release, with no dependencies or blockers.

• Issues related to Open edX aspects and Done XBlocks were clarified:

  • Done XBlocks doesn’t require a named release (internal repo).

  • Open edX Aspects PR was accepted, so future releases will include it.

Teak Release Planning (Next Open edX Release)

• Planning meetings occur every two weeks (next one on Thursday).

• Teak’s current schedule:

  • Branch cut on April 9, 2025

  • Final release on June 9, 2025

• Dates are flexible and subject to adjustment based on product requirements.

• Discussion around why Teak has a 2-month testing window (compared to shorter cycles for Sumac and Redwood):

  • Default scheduling assigns 2 months for testing,

  • Previous releases had shorter cycles due to specific product needs and last-minute feature inclusions.