Agenda

DRAFT

Minutes

Action Items Review

@Herbert Damker to check with marketing the latest date for the content/scope of the Spring25 and the expected marketing date.
Answer: March 15: target date for M5. is OK for input to marketing.
- List of APIs which are part of the spring meta release
- Which quality criteria they fulfil
- Statements of customers about having now a release management and meta releases
- announcements at Cloud Native Telco April 1st, CubeCon April 2-4th CAMARA booth.

Spring25 meta-release

38 APIs in Spring25 within 21 repositories: 14 new APIs and 24 updates from Fall24 (1 abstained: HomeDeviceQoD)

M2

Commonalities 0.5.0-rc.1 & ICM 0.3.0-rc.1 both nearly ready to release r2.2 - RM review done.
Commonalities: do rc.1 one now for API project usage, and do final public release with the embedded changes.

M3

19 API review requests in the backlog (missing for DedicatedNetworks (not expected), DeviceSwap) - RM team needs to speed up reviews.
APIs only doing Comm / ICM updates can wait for the cr release of Comm / ICM
Other APIs shall go ahead and create their (alpha or) rc release so they can be reviewed, especially new APIs.

M5

March 15: target date for M5. is OK for input to marketing.@
- @ Create update of teh marketing slides (technical part on release mgmt)

API specifics

DeviceSwap - keep in Spring25
DedicatedNetworks: no release PR - propose to be moved to the Fall25
CallForwardingSignal wants to release as stable. Before M4 the missing test result statement could be obtained, but not the GSMA certification. - suggest to publish as initial API. - see discussion here: https://github.com/camaraproject/CallForwardingSignal/discussions/115
SimpleEdgeDiscovery - recommend to update according to Herbet’s comment on device object or skip this meta-release

Issues review

20 Spring25 review issues open; two closed (New initial: Tenure and Sandbox: DeviceDataVolume)

AOB