2025-01-20 BTR Meeting Minutes

Newsfeed

Sumac retrospective

• Sumac.1 Retrospective 🌳⏪

@Jorge Londoño

Retrospective for Sumac.1:

• A retrospective space was created in Confluence to gather feedback on the Sumac.1 release process.

• All team members are encouraged to provide comments and suggest improvements over the next two weeks.

• A wrap-up meeting will be scheduled to review the feedback and determine actionable items.

Retrospective action items follow-up

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

@Jorge Londoño

Next release

• sumac.2 ~ 2025-02-09

  • 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

  • teak.1~ 2025-06-09

  • The next Release Planning session is on Thursday 23/01.

@Jorge Londoño

1. Planning for Sumac.2 Release:

   • The Sumac.2 release is scheduled for February 10, 2025, with preparations underway.

   • Jorge will reach out to stage owners (e.g., testing, product) to ensure all required PRs and backports are included in this release.

   • Team members were reminded to highlight any known issues or pending tasks for inclusion in the point release.

2. Planning for Teak Release:

   • The master branch will be cut on April 9, 2025, with the testing process running until the release date on June 9, 2025.

   • Jorge will raise this schedule during the next community meeting to confirm or adjust the proposed dates.

3. Repository Issues and Improvements

• Tagging Issues in Repositories:

  • Farhaan identified missing release tags in two repositories.

  • The absence of the required openedx.yaml keyword caused these repositories to be excluded from tagging since Redwood.

  • Action items:

    • Farhaan will manually tag the branches and open PRs to add the missing keywords.

    • He plans to use repo tools to identify other potentially affected repositories and ensure all are properly tagged for future releases.