Agenda

The project's Antitrust Policy is linked from the LF and project websites. The policy is important when multiple companies, including potential industry competitors, are participating in meetings. Please review it, and if you have any questions, please contact your company’s legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

• Action Items Review

• Discussion Review

• Spring26 meta-release

• Issues review - Release Management

• Issues review - CAMARA Project Administration (repository)

• AOB

Minutes

• Approval of previous meeting’s minutes: approved.

Action Items Review

• See action items list here: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14552660

  • link to automation wish list wiki page: https://lf-camaraproject.atlassian.net/wiki/x/GYADC

  • no particular points raised

Discussions Review

• See camaraproject/ReleaseManagement · Discussions · GitHub: No new discussion.

Spring26 meta-release (https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/268500993 )

• New Spring26 and Fall26 schedules, and generally the new meta-release schedule were approved in the TSC on Nov 6. The below pages were updated to remove the preliminary warnings.

  • https://lf-camaraproject.atlassian.net/wiki/x/AQABE

  • https://lf-camaraproject.atlassian.net/wiki/x/AYABE

• New meta-release naming : TSC to close out Meta-Release Naming — Community Discussion · Issue #200 · camaraproject/Governance . Vote resulted in choice of YYYYH1 / YYYYH2. Action with Marketing

M1

M1 Commonalities & ICM (Nov 30)

• Cut-off date for features to be included in the scope of Spring26

• Commonalities Spring26 scope issue: Scope of the Spring release #543

  • Commonalities will skip the M1 alpha release - API teams can check the Commonalities milestones for status.

• ICM Spring26 scope issue: ICM scope for the Spring26 meta-release #311

M1 APIs (Dec 15 - Spring26 is not recommended for APIs)

• Requests for Spring26 participation are to be done through a GitHub issue in Release Management

• @Tanja de Groot send email to codeowners list indicating that there should be an important reason for the release in Spring26, like late drop out from Fall25 or updated initial APIs that did not target Fall25, or initial APIs that can meet the steep timeline of Spring26, or initial APIs from previous meta-release(s) that have urgent feature update request.

• release can be done at any time

M2

• Target date is Jan 31, 2026 for the release-candidate of Commonalities & ICM.

M3

• Due on Jan 31, 2026 for Spring APIs that have been granted participation.

Issues review - Release Management

See Issues · camaraproject/ReleaseManagement - progress is logged in the issues

Issues review - CAMARA Project Administration (repository)

• Repository link: project-administration

• Herbert presented the latest progress on the Release Mgmt automation plans.

AOB

• NONE

Action items