Versions Compared

Version Old Version 2 New Version Current
Changes made by

Tanja de Groot

Tanja de Groot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Community Attendees:

Herbert Damker Tanja de Groot

Community Attendees:

LF Staff:

Evan Harrison Casey Cain

Agenda

DRAFT

Antitrust Policy

  • Action Items Review

  • Spring25 meta-release

  • Issues review

  • AOB

Minutes

Action Items Review

See previous minutes: 2025-02-04 Release WG Minutes - CAMARA Project - CAMARA ProjectSpring25

xx APIs in Spring25 within yy repositories: zz new APIs and 24 updates from Fall24 (1 abstained: HomeDeviceQoD)

    • Applied in Spring25 by OTPvalidation and NumberVerification

Spring25 meta-release

  • 13 new APIs and 22 updated Fall24 APIs (of 25) are candidate for Spring25. Total of 35 APIs in 19 API repositories

  • Two Sub Projects decided to skip the Spring25 and go to Fall25:

    • dedicated-networks, as still under design

    • simple-edge-discovery which will take the time to do a redesign to better align with CAMARA guidelines.

  • Some APIs were moved to Sandboxed APIs (APIs not yet in any meta-release)

  • Tanja de Groot to update the excel on status of Spring25 meta-release APIs → done

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

  • 2 APIs decided to skip

last week:

  • 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.0-rc.1 - only applicable for APIs that do a patch or minor update (x>0) for Spring25 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/CommonalitiesSpring25 and go for release in Fall25: DedicatedNetworks and SimpleEdgeDiscovery. There may be 1 or 2 more. Finale decisions will be made at TSC on Feb 20.

  • Call out to finalize release-candidates on All Hand Call on Feb 13

M4

  • Feb 28th

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

Tanja de Groot : list the critical ones for the TSC - needing more than a days effort.

Result: M3 review status analysis excel: View filenameSpring25_M3_Progress_v1.xlsxAll remaining issues were reviewed.

Action items

  •