2025-11-18 Release WG Minutes
Community Attendees:
Community Attendees:
LF Staff:
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: Release Management Working Group
link to automation wish list wiki page: CAMARA Release Process - Coverage of Fall25 Release PR checks
@all to review the CAMARA Release Process - Coverage of Fall25 Release PR checks table.
@Tanja de Groot to propose merge of the Release Management process documentation in GitHub with the new process trying too simplify it. Target readiness by the AHC on December 11.
Discussions Review
See camaraproject/ReleaseManagement · Discussions · GitHub: No new discussion.
Spring26 meta-release (Spring26 meta-release )
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.
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 December 11. (check slide).
New meta-release naming : TSC to close out
Meta-Release Naming — Community Discussion · Issue #200 · camaraproject/Governance .
M1
The M1 date in the new preliminary schedule is nov 30 (see Spring26 meta-release )
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
Issues review - CAMARA Project Administration (repository)
Repository link: project-administration
Herbert showed the sub issues created for the issue Release Collector Workflow - Release reporting · Issue #34 · camaraproject/project-administration
Herbert showed the Three Reporting Workflows for CAMARA Repository and Release Management · Issue #38 · camaraproject/project-administration. Outstanding action for all to review.
@Herbert Damker Create a sub issues under #191 Develop automation support in support of release management to define the schema and create an artefact repo in RM repo to hold it.
Rafal explained that “Linting how to” may be moved from commonalities to tooling
Tooling project: @Rafal Artych to close tooling issue #9
AOB
none