2025-05-27 Release WG Minutes
Community Attendees:
@Tanja de Groot @Rafal Artych
Community Attendees:
@Herbert Damker Cyndi Lin (Aduna) @Surajj Jaggernath
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
Fall25 meta-release
Issues review
AOB
Minutes
Action Items Review
See action items list here: Release Management Working Group
Action on versioning is pending on final text agreement
Discussions Review
No new discussion.
Fall25 meta-release (Meta-release Fall25)
M1
Release r3.1 of Commonalities is available – with restructured, easier to read guideline documents:
No impacts on APIs with breaking changes (Analysis of Commonalities 0.6.0-alpha.1)
Still some issues pending which need to be resolved (event versioning, testing template for subscriptions, etc.)
Release r3.1 of ICM available – no impact on APIs beyond documentation
Release Management to update its Wiki and GitHub artifacts for the Fall25 (alpha release at M1) - preparation ongoing
Currently 53 APIs proposed for the meta-release (numbers are not final as API repository teams can decided until M3 milestone to participate), thereof
25 new APIs
28 updated APIs, thereof 7 stable APIs
M2
Release-candidate of Commonalities and ICM - June 7 - PRs expected to be ready
Commonalities call shifted to June 16 due to holiday on June 9
M3
First release-candidates of APIs - Jun 21
Issues review
Information has been documented in the issues.
For event versioning, still some open points on the documentation need to be resolved before creating the PR.
Test result statement for stable APIs within Spring25 meta-release (M4) · Issue #161 · camaraproject/ReleaseManagement - target date for closure: Apr 29, 2025 - this issue is kept open and will be left to the teams to manage and give credibility to their APIs. This shall be managed latest for the next release of these APIs. This will be closed by M3.
Skipping meta-releases - the active API list will be based on the last 3 meta-releases only, i.e. list of “meta-released” APIs
@Tanja to set a call on event versioning next week: Herbert, Rafal, Ludovic, Pedro. Need to have the PR by end of next week. Later consider the case of a separate event definition files.
AOB
Herbert showed automation of meta-release report creation
Discussion on repo lifecycle: independent sandbox and Sub Project sandboxes could have separate states. @Herbert to think about improving the Sandbox related project structure
Independent sandbox can evolve to its own API Sub project or be adopted by an existing one.