2025-11-04 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
Release schedule update
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: 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
Explanation on milestone usage by Commonalities has been added to #327 Check how to use milestones for Commonalities and ICM progress checking
Discussions Review
See camaraproject/ReleaseManagement · Discussions · GitHub: No new discussion.
Spring26 meta-release (https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/268500993 )
M1 schedule
The M1 date in the new preliminary schedule is nov 30 (see https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/268500993 )
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.
Release Management will
present the concept of the release-plan.yaml files to TSC
present the new approach and what the API Sub Projects need to do in the AHC on November 13.
M1 Commonalities & ICM
Commonalities and ICM are preparing content for 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
Tanja to check if M1 is skipped
M1 APIs (Spring26 is not recommended for APIs)
Recommended to skip Spring26, but exception may exist e.g. for APIs that dropped from the Fall25 meta-release.
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.
Release schedule update
New meta-release schedule proposal following the feedback in Dual Phase proposal.
These pages are open for review until the TSC of Nov 6th
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.
Issues review - Release Management
See Issues · camaraproject/ReleaseManagement - progress is logged in the issues
API patch releases should apply https://lf-camaraproject.atlassian.net/wiki/x/AQC3Eg
error info schema was applied to all Fall25 APIs
@Tanja to reference #327 in #332
wishlist to be updated to become a table to put where to resolve the automation - workflows/phases, spectral rules, @Herbert Damker
Issues review - CAMARA Project Administration (repository)
repository link: project-administration
@all to review the PR on the meta-release collector (at least the princple)
@all to review the templates in 32
Could support external dedicated reporting
AOB
none