2025-12-16 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: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14552660
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.
New meta-release naming : TSC to close out https://github.com/camaraproject/Governance/issues/200 . Vote resulted in choice of YYYYH1 / YYYYH2. Action with Marketing.
M1
M1 Commonalities & ICM (Nov 30)
Commonalities Spring26 scope issue: Scope of the Spring release #543 is frozen.
ICM Spring26 scope issue: ICM scope for the Spring26 meta-release #311 is frozen.
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
Spring 26 participation: SessionInsights #350 - fall25 drop-out - OK for Spring26
Spring26 participation: Network Slice Booking #341 - major redesign needed for the new API - could release their first API if updated
Release Management has discussed and is OK for the candidates to participate in Spring26 - the final decision will be the M3 milestone (Jan 31, 2026) for which solid API definition(s) are expected.
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
Issue Create the template of a review request for independent API releases · Issue #346was discussed in the release management meeting and subsequently closed:
API projects who want to do an independent release can request the review by release-management_reviewers once their API alpha or release-candidate is ready according to the team
Release Management team will create a review issue in the Release Management repository for tracking the requests using an already available template
Issues review - CAMARA Project Administration (repository)
Repository link: project-administration
finalize (merge) https://github.com/camaraproject/ReleaseManagement/pull/339 (Add CAMARA release metadata schemas) as this is the prerequisite for the further work towards roll-out - done
discuss https://github.com/camaraproject/ReleaseManagement/issues/347 (Define production URLs for Release Collector viewers on camaraproject.github.io) to be able to close the work on Release Collector and its viewers before the year-end break - done
How it would look like can be seen in my test pages: https://hdamker.github.io
The following PRs are prepared and ready to be merged for the deployment of the release viewers:
AOB
presentation on new release process was done to the AHC. - slides uploaded to the release management repo.
@Casey Cain please cancel the Release Management meetings of Dec 23 and Dec 30
Holiday schedule
Tanja - Dec 22 - Jan 5
Herbert - Dec 19 - Jan 5
Dec 23: Meeting cancelled
Dec 30: Meeting cancelled