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

• Herbert to check with Rafal Artych on how we can progress the automation support (tooling/issue 9) - done.

Discussions Review

• See camaraproject/ReleaseManagement · Discussions · GitHub

• No new discussion.

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

M2

• RM release PR should also be coming soon.

M3

• TSC on Jun 19 moved the M3 date to Jun 28. Decision expected on TSC of July 3, 2025.

• Currently 62 APIs proposed for the meta-release (numbers are not final as API repository teams can decided until M3 milestone to participate), thereof

  • 27 new APIs

  • 35 updated APIs, thereof 11 stable APIs (of which all 9 stable APIs from Spring25 and 2 first-time stable APIs)

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

Analysis by Herbert of the current state of M3 review submissions:

THere are now 33 repositories with release PRs and release review issues, of which

7 are still in draft mode (in alphabetic order):

ConsentInfo

• PR in draft mode

• 2 PRs pending

• test definitions yet missing

DeviceLocation

• PR in draft mode

• About 9 PRs open to be merged

KnowYourCustomerAgeVerification

• Release PR has currently only the CHANGELOG.md

• Recommended to put into draft mode for now

ModelAsAService

• Release PR set to draft mode (work ongoing)

• 3 APIs

QoSBooking

• Release PR set to draft mode

• 3+ pending PRs

QualityOnDemand

• Multiple dependent PRs open, merge conflicts to be resolved

• Release PR content not yet complete, in draft mode

VerifiedCaller

• Two APIs, but only one release tracker?

• Asked for clarification

There are 7 repositories which don't have yet a release PR but are more or less on the way ... in descending order of confidence that they will make it:

DeviceReachabilityStatus
DeviceRoamingStatus
ConnectedNetworkType

• Multiple promising activities in last week, but no release PR yet

PredictiveConnectivityData

• One functional issue open from scope open without PR

• PR for alignment with Commonalities 3.2 in work

SessionInsights

• API YAML in good shape, test definition file with basic tests missing

ConnectivityInsights

• One PR with alignment changes open (commented on it)

• Release PR “will come next”

ApplicationProfiles

• No sign of release PR yet

• PR with functional enhancement open, opened just on June 26th

An finally here are the candidates which we can / should exclude already  from Fall25:

NetworkAccessManagement

• Many open issues, issues in scope issue of Fall25 are still all open, no PRs on them

• No sign of release PR yet

• Size of API definition untypical for CAMARA (3465 lines) … split considered but not done

• Recommendation: do initial release outside of meta-release cycle

WebRTC

• See https://github.com/camaraproject/WebRTC/issues/82#issuecomment-3016869238

• No visible activity towards a Fall25 release

• (we shouldn't allow them again to produce work during the review phase)

HighThroughputElasticNetworks

• No yaml, no open PR, placeholder scope item

IoTSIMFraudPrevention

• No yaml, no open PR, no scope item

Issues review - Release Management

• Issues · camaraproject/ReleaseManagement

• 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

1 issue to be done shortly

AOB

• @Herbert Damker to add Kevin and Jose Luis to the reviewers list

• Automated linting rules to be introduced between M3 and M4 plus some possible extensions

• July / August reviewer (non-)availability:

  • Tanja: all of August

  • Herbert: first half of August

Action items