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 - Release Management

  • Issues review - CAMARA Project Administration (repository)

  • AOB

Minutes

Action Items Review

• See action items list here: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14552660

• Sandboxes have been properly separated both in GitHub and on Wiki (so Herbert can stop thinking ). - action closed

Discussions Review

• See camaraproject/ReleaseManagement · Discussions · GitHub

• No new discussion.

Fall25 meta-release (https://lf-camaraproject.atlassian.net/wiki/x/FQApAg?atlOrigin=eyJpIjoiZWIyZGY3YWY4Yzk2NGQxNWFjODlkZGNmYmFmYTVkMDIiLCJwIjoiYyJ9)

M2

• Release Candidate r3.2 · PR #295 · IdentityAndConsentManagement available – no impact on APIs beyond documentation

• Release 3.2 · PR #478 · Commonalities - release PR available for review

  • @Rafal Artych to update PR on review issue to include addition checkpoints

  • @Rafal Artych to add an indicator to the Commonalities Analysis of Commonalities 0.6.0-rc.1 changes on differences between r3.1 and r3.2

• M2 expected to be declared by TSC on June 19.

  • Herbert has kindly accepted to stand in for Tanja on Release Mgmt report as she cannot make it to this TSC.

• RM release PR should also be coming soon.

M3

• First release-candidates (release PRs) of APIs - Jun 21

• M3 review issue is available for use. Currently 61 APIs proposed for the meta-release (numbers are not final as API repository teams can decided until M3 milestone to participate), thereof

  • 30 new APIs

  • 31 updated APIs, thereof 9 stable APIs (of which 2 first stable APIs)

  • 37 repositories

• It is expected that a number of the new initial APIs may not make it into the meta-release - read the docs, team-up with experience team members

• Review questions:

  • Can we automatically create a PR to update the API readiness checklist with row 13  ? - yes, @Herbert to create an automation

  • Should we introduce the XCorrelator schema definition already ? - YES

  • Where is the readme template ? - https://github.com/camaraproject/Template_API_Repository/blob/main/README.md

  • What should be in ? e.g. the links to swagger etc. - no not required, it is up to the API Sub Projects.

  • Update done by automated process is indicated in the PR file, but it is not visible what has changed, and the addition changes the line references of the review comments. - bad luck !

Issues review - Release Management

• Issues · camaraproject/ReleaseManagement

• see issues. @Tanja de Groot to update issue #221 on version number structure and transfer to Commonalities.

• 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.

Issues review - CAMARA Project Administration (repository)

project-administration repository: project-administration

We forgot to address this point.

AOB

• none

Action items