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: no comments, approved.

Action Items Review

• See action items list here: Release Management Working GroupPreview

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

  • actions were checked but most are still open

Discussions Review

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

Spring26 meta-release (Spring26 meta-releasePreview )

• 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

• Also the base concept of the release management automation, based on release-plan.yaml files, was presented to TSC

• A similar introduction presentation will be done on the AHC on November 13. (check slide).

• New meta-release naming : please check & comment https://github.com/camaraproject/Governance/issues/200 .

  • TSC - ask for resolution proposal e.g. a vote of top list - decision in the TSC after that. @Herbert Damker will summarize the status in the issue and send to TSC.

  • Vote to been opened by Casey.

    • Voters: TSC Participants + Outreach Committee needs to be clarified

    • Need to open 2 votes and add the results (due to system restrictions)

    • @Casey Cain to check with @Herbert Damker on the voting scope.

M1

• The M1 date in the new preliminary schedule is nov 30 (see Spring26 meta-releasePreview )

  • Note: APIs are recommended to target the Fall26 Meta-release, but some exceptions can be discussed.

  • For these exceptions, the concerned APIs should be aware that the Spring26 schedule is very tight.

M1 Commonalities & ICM

• 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 (Spring26 is not recommended for APIs)

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

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

• badges for test statements:

  • can be assigned to repositories

  • needs design, needs a clear list/justication/guideline (goals, requirements, etc)

  • should be automated (using workflows) based on meta-data

Issues review - CAMARA Project Administration (repository)

• repository link: project-administration

• Issue reviewed, remain open.

AOB

• none

Action items