Agenda

DRAFT

Minutes

Action Items Review

No actions

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 released as r2.2. Some documentation updates planned for the public release.
Public releases: latest 2 weeks before M4 (target: Feb 14)

M3

WebRTC API review - very Telco focused, no test files yet. How to progress APIs in this state at M3 ? - to be discussed in TSC.
Question on versioning: for a release v0.3.1-rc.1 is the url part: v0.31rc1 ? for the release candidate (not the public one) →
- for M4, upcoming, should the public url be v0.31 or v0.3 ? – should be v0.3
- Question: The URL for a release candidate of version 1.1.0, if there was previously already a release candidate for 1.0.0 ...
  ... the URL can't be again v1rc1, as this URL existed already before, so could use: v1.1rc1
  ... v1rc2 could be an option ... which would imply that the version is v1.1.0-rc.2 ... so the number of behind the release candidate will be used only once per major version
proposal use the full version in the url (e.g. v0.3.1-rc.1 / v1.1 - only applicable for APIs that have the patch minor updat (x>0) issue and to generalize in the next meta-release. create an issue in Commonalities for this point @Tanja de Groot
Done: Issue created: Update of versioning guidelines for the url field · Issue #405 · camaraproject/Commonalities

M5

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

Issues review

Issues · camaraproject/ReleaseManagement

Number Recycling: @Herbert to check with DT API team

To do: list the critical ones for the TSC - needing more than a days effort.

AOB