Page History

...

• EasyCLA Introduction (Casey Cain Herbert Damker )
  • People from multiple companies have done successful test PRs on https://github.com/camaraproject/EasyCLA
    • Including Deutsche Telekom, Orange, KDDI, Vodafone, Telefonica
    • Please use the chance to ensure that you have a signed CLA before it will get activated on all repositories, by opening a short test PR here
    • In case of any problem reach out to Casey Cain 
    • Activation on September 2nd (according to last TSC)
• Preparation of Meta-Release announcement will be prepared by Marketing Working Group in cooperation with Release Management working group
• ...

Commonalities (Rafal Artych )

• Release r0.4.0-rc.2 as release second release candidate with bug fixes created on August 9th
  • Fixed bugs as listed in Commonalities/issues/253
• Minor changes since then:
  • ...
• Pull request for public release to be approved today: ...
• ...

Identity & Consent Management  (Axel Nennker )

• Release r0.2.0-rc.2 as second release candidate with bug fixes created on August 1st
  • Change of mandatory text has been addressed across all API release candidates
  • No further changes since then
• Pull request for public release to be approved today: ...
• ...

Release Management (Initial content by Herbert Damker on behalf )

• Meta-release Fall24 - CAMARA Project - Confluence
  • M3 Milestone (release candidate of APIs) achieved for 21 APIs (as of August 21st)
    
    • Overview of the available release candidates (as of August 16th):
      • Stable APIs (target v1.0 version, previous API versions launched by operators): 
        location-verification, number-verification, one-time-password-sms, simple-edge-discovery, sim-swap
      • APIs with updated initial versions (previous launched by operators): 
        carrier-billing, device-reachability-status, device-roaming-status, home-devices-qod, kyc-fill-in, kyc-match, quality-on-demand
      • "New APIs" (some with previous initial versions or split out of other APIs):  
        call-forwarding-signal, carrier-billing-refund, device-reachability-status-subscriptions, device-roaming-status-subscriptions, geofencing-subscriptions, population-density-data, qod-provisioning, qos-profiles
    • One open review issue of a release candidate (ConnectivityInsights) with connectivity-insights, application-profiles (as of August 21st)
      • Proposal to still include (hopefully done as of TSC time)
    • Excluded from Fall24 meta-release: network-slice-booking (no YAML yet), network-access-management (not time to address review results, will go for Spring25), WebRTC (no release tracker, no response during M3)
  • M4 Milestone (Public releases) - next steps and dates
    • August 26th (M4 release PRs available): Sub Projects should have prepared the release PRs for the public API version(s), including the release notes in CHANGELOG.md which are reflecting all changes since the last public release. Invite camaraproject/release-management_maintainers for review, don't merge before have the approval
      
      • If there are outstanding PRs (e.g. with test definition files) anticipate them and add remark within the release PR description that these have to be merged before
    • August 30th (M4 date): all outstanding PRs merged which have to done before the creation of the public release (e.g. test definition files)
    • September 5th (Approval of M4): all release PRs of Sub Project reviewed by Release Management, final approval of the Fall24 participating API releases within the TSC.
  • M5 Milestone: all release PRs merged and public releases created.
• Next release cycle (Spring 25"Spring25") starts at September 30th (M0 - Kickoff)

...