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)

• Tooling

• 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

• Rafal action completed - 8 sandbox are still missing. Action @Herbert Damker to update the reporting workflow to reflect linting integration

  • Manual update done of SimpleEdgeDiscovery API

Discussions Review

• See camaraproject/ReleaseManagement · Discussions · GitHub: No new discussion.

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

M4

• 40 Fall25 M4 review issues for APIs are opened covering all repositories participating in the meta-release

  • M4 declaration: target date is September 16 (Release Management meeting)

  • M4 review status:

    • see links created by Kevin in RM chat here: https://camara-project.slack.com/archives/C090WU7PL9Y/p1757343252252089

    • 18 M4 review issues with comments by RM team (filter = "- [x] Review comments provided (on behalf of Release Management)" )

    • 5 M4 review issues with RM comments integrated by API teams (filter = "- [x] Review comments addressed (by release PR editor)" )

    • 22 M4 review issues still need RM review (filter = NOT "- [x] Review comments provided (on behalf of Release Management)" )

  • Decision to start doing approvals of the release PRs: yes go for approvals

• Commonalities 3.4 M4 review

  • Release Management team proposes that @Rafal Artych discusses with the Commonalities team next monday:

    • Do the Commonalities patch release after Fall25 M4. so APIs will only refer to r3.3 in the meta-release

      • Once the Commonalities patch is released, if an API patch release is done, it should include refer to r3.4.

    • Commonalities includes also some further minor fixes

    • Examples of addition small changes that could be included in the patch:

      • see Fix: networkAccessIdentifier uses a real domain name in its schema example · #529 for example on network access identifier should refer to “Example Domain ” (NOT “domain.com” which is a commercial website). Same for “supertelco.com”

      • don’t use full tokens

      • careful with phonenumbers

      • domain names

    • Gherkin linting

      • special linting config was done for kyc-match

      • a rule could be changed in the main linting configuration as well to avoid the error.

      • today it does not block the merge

      • @Rafal Artych Let's make Toshi and Kevin happy and update the rule

      • may need to reset the context to apply the new rule (e.g. close and reopen the PR - @Herbert Damker to support)

M5

• M5 date: target is declaration in the TSC meeting on September 18.

• Marketing target event - proposed: Webinar on e.g. Oct 9. Press release a week before.

Issues review - Release Management

See Issues · camaraproject/ReleaseManagement - progress is logged in the issues

• Decide how to handle the ErrorInfo schema order issue within the M4 release issues - #323 - to be closed @Tanja de Groot

• Test result statement for stable APIs within Fall25 meta-release (M4) - open

• Include only relevant documents into released archives - #299 - converted to Q&A discussion - needs closing remark and change to answered. @Tanja de Groot

• Template for Release Information section in README.md needed - #273 - discussed input provided by Tanja in the issue

• Change structure of event version - #221 - to be done @Tanja de Groot - to be included in Spring26 scope of Commonalities

• Develop automation support in support of release management - #191 - keep open - check what has been covered first then close. continue on wiki (wish list with checkboxes), in tooling and in issue #257

• Test result statement for stable APIs within Spring25 meta-release (M4) - #161 - action by Tanja ongoing - waiting for 2 API teams to close their issue.

Release Management automation

• #257 CAMARA Release workflow and metadata proposal

  • All comments were addressed - @Tanja de Groot to check latest

Issues review - CAMARA Project Administration (repository)

project-administration repository: project-administration

• #21 Update "Ops Playbook" regarding outdated topics

• new issue created on the meta-release reporting work flow (demo done and great job by@Herbert Damker ). Check usage in parallel with current Confluence approach

• new issue on policing work flow is to come

Tooling

• see above (Project Administration)

• Rafal created a results page for the project-administration linting flows under Tooling:

  • See Centralized linting roll-out - CAMARA Project - CAMARA Project

AOB

• N/A

Action items