2025-10-28 Release WG Minutes
Community Attendees:
@Herbert Damker @Rafal Artych @Alberto Ramos Monaga @Tanja de Groot
Community Attendees:
LF Staff:
@Casey Cain
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
Once APIs have entered a meta-release, they should no longer show on the https://lf-camaraproject.atlassian.net/wiki/x/4YAlAg page.
Linting status is now accessible here: https://lf-camaraproject.atlassian.net/wiki/x/TACuCw
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 exception, the concerned APIs should be aware that the Spring26 schedule is very tight.
Release Management to
define and roll out the release-plan.yaml files for the current API versions to API Sub Projects @Tanja de Groot to approve the PR
update wiki / github API process - RM team to decide how to integrate this info to the documentation for API teams.
AHC in November: present the new approach and what the API Sub Projects need to do
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
M1 APIs (Spring26 is optional for initial 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
for real deployments GSMA map is the reference
How to motivate the stable pre-M4 testing and related test statement ? Ideas welcome.
Check if test-statement is represented in the meta-data ? (check that checklist items are in the meta-data)
will be integrated into main camaraproject
do an easyCLA check with the bot
test roll out to a few repos
roll-out to all publicly released APIs (Fall25) by creating a PR in each API project
change the API repository template to fit the same scheme (add delimiters)
apply it all non-released APIs (needs more work)
Issues review - CAMARA Project Administration (repository)
repository link: project-administration
status quo
AOB
Move the meeting 1hr later after daylight saving time - support team is working on it - done