Agenda

Minutes

Action Items Review

See previous minutes: 2025-02-18 Release WG Minutes

On issue: Update of versioning guidelines for the url field · Issue #405 · camaraproject/Commonalities: proposed solution was to include full version number in url for alpha and release-candidate APIs was rejected and a new issue is opened for Fall25: #158.
- OTPvalidation and NumberVerification: open an issue for each API and create a new release-candidate applying Spring25 versioning guidelines Jose Luis Urien Pinedo PRs to be done by Herbert Damker. - Done. a r2.2 was created for each API.
check at the same time where to
- Check where in the repositories we can optimize release / version number changes Herbert Damker:
?
- tbd
Tanja de Groot to create a new issue in WebRTC with review comments - done Post M3 Release Management review issue (to be used for M4) · Issue #70 · camaraproject/WebRTC
Change back Sandboxed → Sandbox Tanja de Groot - done: Sandbox APIs
Rafal Artych to provide the exact guideline - done: https://lf-camaraproject.atlassian.net/l/cp/WpqFXLjC
Herbert Damker to update the review template for M4 reviews - done and in use
Tanja de Groot Mail after TSC on start of public release review cycle and updates needed for M4 - done

Spring25 meta-release (Spring25)

13 new APIs and 22 updated Fall24 APIs (of 25) are candidate for Spring25. Total of 35 APIs in 19 API repositories
Some APIs were moved to Sandbox APIs (APIs not yet in any meta-release)
- Do we have all Sandbox API pages ? if not, should we get them and how ?

M2

M3

M3 declared by TSC for Fevb20th: API reviews remaining (see Issues review below
- WebRTC and xxx were published without RM approval but post M3 comments have been provided in dedicated issues and are being addressed, if possible for M4

M4

Review issues are starting to be created with explicit Commonalities alignment points to be checked listed in the review issue. Assignment to be done elow.
target date for public release PRs: Feb 28th
target date for reviews: tbd

M5