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: Release Management Working GroupPreview

• README harmonization to be applied after M4 is done.

  • “solved by M5 “ is OK.

  • issue #273 to be closed by then. other action closed as pursued in this issue.

Discussions Review

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

Fall25 meta-release (Fall25 meta-releasePreview)

M4

• M4 review issue template is now agreed and includes the additional checks from Commonalities r3.3 public release.

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

  • M4 declaration: target was Aug 31. Communicated to TSC on Sep 4 that all release PR are available - provide edge cases as needed. M4 pushed out till after the reviews to Sep 15 (with M5 in TSC of Sep 18).

    • think about badges and allocation criteria - Casey ca support creation.

  • 3 still have DRAFT release PRs - should be finalized this week

  • 12 are marked as “reversed”: Herbert to explain: related to the discrepancy between error data types in yaml and in Commonalities guidelines - we do not want the order to be reversed (if not done yet) - order will be: status, code, message

    • this is not a client breaking change. yaml examples are OK

    • API providers may anticipate a maintenance release (Commonalities r3.4 / v0.6.1) - see issue #526

    • another update could be a change to feature files - reference to NetworkAccessIdentifier

    • reviewers should handle case by case (discus on chat as needed)

  • available reviewers please self-assign bottom up from the issues list

M5

• M5 date: target September 15; announce in TSC on September 18.

• Marketing target event - proposed: week after TSC e.g. thursday Sep 25.

Issues review - Release Management

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

• #161 Test result statement for stable APIs within Spring25 meta-release (M4)

  • Can be closed as #303 takes over - close the API repo one first with link to #303 - and then this one @Tanja de Groot

  • A new parent issue has been created to point to new sub-issues asking for a Test result statement for stable APIs within Fall25 meta-release (M4) - #303: Test result statement for stable APIs within Fall25 meta-release (M4)

• #191 Develop automation support in support of release management

  • keep open - check what has been covered firstn then close. continue on wiki (wish list with checkboxes), in tooling and in below issue #257

• #200 [API Backlog] API description as Meta-Release deliverable

  • has been closed

  • consider adding a link to the API description in the README file - create a new issue @Tanja de Groot

• #221 Change structure of event version

  • @Tanja to add context before transfer to Commonalities

• #273 Template for Release Information section in README.md needed

  • PR has been created and is open for review

  • Template to be defined possibly with custom part or an “Additional Information” section. To be solved by M5 - @Tanja de Groot to prepare proposal

  • Herbert will take a look if possible also for automation

• #299 Include only relevant documents into released archives

  • Can be closed - @Herbert to provide the links

• #302 List of outstanding Fall'25 M4 PRs

  • closed as done

• #323: Decide how to handle the ErrorInfo schema order issue within the M4 release issues

  • basic guide for reviewers: recommend that API projects anticipate using the one in the API Design Guidelines ((http) status, code, message), while still referencing Commonalities 3.3

  • for APIs who have release PR available and the “wrong” approach - do a review comment to consider anticipating the “right” approach. ( Commonalities PR #517 )

Release Management automation

• #257 CAMARA Release workflow and metadata proposal

• Review comments provided by the team and invited reviewers

• Concept planned for September and tested for Spring26 by some APIs

Issues review - CAMARA Project Administration (repository)

project-administration repository: project-administration

• #21 Update "Ops Playbook" regarding outdated topics

• @Herbert Damker will roll out central linting to all the repositories in Fall 25 (after M5)

• @Rafal Artych to complete the table of the repos outside Fall25 that require to add linting introduction PR

Tooling

• see above (Project Administration)

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

  • Done, see Centralized linting roll-out - CAMARA Project - CAMARA Project

AOB

• Thanks to Kevin and Herbert for running the August meetings and providing the minutes !

Action items