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

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

• Atction Rafal: make Toshi and Kevin happy and update the linting rule to avoid the kyc-match error done and Fabrizio is happy too.

• Herbert Damker to update the reporting workflow to reflect status of a repository with linting integration - ongoing as part of the repository status workflow covering various checks.

• Tanja de Groot consider adding a link to the API description in the README file - create a new issue - should point to the website (not wiki)

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 participating in the meta-release

  • M4 review status:

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

    • 22 API repositories have been released

    • 17 API repositories have been reviewed by Release Management

      • are there any review with big issues ? No

    • 1 API repository review is in progress by Release Management (ApplicationEndpointRegistration)

    • ScamSignal API to be done as well. @Tanja de Groot

  • M4 declaration: approval of M4 in the September 16 Release Management meeting: will be reported in the TSC on Sep 18 - Fall25 meta-release page will be updated for thursday; CAMARA home page will be updated after the synch meeting with GSMA on friday. draft PR will be prepared already by @Herbert Damker

    • updates on the CAMARA website are being applied “on the fly”.

    • ScamSignal API

      • should update ScamSignal API version to v0.3.1 @Herbert Damker to update the link.

        • CAMARA Project has a footnote: “(2) One additional API, Scam Signal (v0.3.0), was released following the Spring25 meta-release guidelines. This API is developed by and only available on demand through GSMA Open Gateway. For more information, please see the Scam Signal API description.”

      • the note 2 also wrongly mentions already “Fall25” for ScamSignal v0.3.0. this should “Spring25” - maybe not needed to correct this now ?

• Commonalities 3.4 M4 review

  • Release Management team proposed that @Rafal Artych discusses with the Commonalities team0:

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

    • Feedback: no issue to delay after Fall25 M5

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.

Spring26 meta-release (https://lf-camaraproject.atlassian.net/wiki/x/AQB_Cg)

• Commonalities and ICM are preparing content for Spring26

  • Request to consider to change the M1 date for Commonalities, and more generally make a new time plan for the meta-release based on the new approach by M0.

  • Proposal to be prepared by Release Mgmt team for discussion with Commonalities / ICM and in next TSC end of september

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

  • proposal status

  • Agree on content of release plan and release meta-data

  • Needs json schema for the metadata

• Many warnings in spectral (missing description, All of, pascalCase (ex. Http), etc.) - this requires custom functions or configuration - should be addressed

  • artifact from Commonalities should be “clean” from linting perspective

Issues review - CAMARA Project Administration (repository)

• project-administration repository: project-administration

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

  • need to check the “whish list”

  • needs to be separated per “step” - CI (custom spectral rules, home rules), release branch creation

AOB

• N/A

Action items