/
Announcements by Release Management

Announcements by Release Management

This page is to prepare the announcement of milestones or other events from the release management team.


Getting started with Release Automation & Validation

2026-04-29 Special announcement (to: codeowners; cc: TSC, ReleaseManagement)

Dear all,

We are happy to announce that Spring26 ICM (r4.2 / public 0.5.0), Commonalities (r4.2 / 0.8.0-rc.2), and the updated Release Automation and Validation processes are now available for use by the API teams.

Note: See Commonalities r4.2 detailed information and migration guidance: https://lf-camaraproject.atlassian.net/wiki/x/AYBJKw

We recommend:

  • for APIs that have already done a release using automation:

    • independent APIs

      • if currently alpha: please create a next alpha release

      • if currently release-candidate (rc): please create the next rc release

      • if currently public: please plan the next target API version as alpha

    • Spring26 APIs: please create the next rc release

  • for APIs that are onboarded to automation but have not yet released with it: please plan your release in release-plan.yaml

  • for APIs not yet onboarded to automation, start preparing release-plan.yaml.

What this means for codeowners

When you plan your first or next automated release by merging a release-plan.yaml with target_release_type other than none, we will onboard your repository by the next working day, if needed. You will then see automated PRs appear as follows:

  • for onboarding to automation only: a caller-workflows PR adds the Release Automation and Validation workflows to your repository

  • then, a common-file PR is created after the first run of Release Automation, populating your repo’s code/common/ folder with the common files from the referenced Commonalities version (for commonalities_release: r4.2 only).

    • Note: $ref usage avoids manual maintenance/copying of common schemas. For an example, see: Commonalities/artifacts/api-templates at r4.2

    • Note: the Release Automation workflow supports the “bundling” process which produces a single self-contained API YAML from the source API definition and the common file(s) for publication only. It does not impact the source API definition on main.

→ @all codeowners: please review and merge such PRs as soon as they become available.

From then on, the Validation workflow will run automatically on every PR and posts its findings in the PR.

  • Codeowners are encouraged NOT to merge PRs with validation errors, but merge is not blocked.

  • Release snapshot creation is blocked when Validation reports errors — this is the hard gate.

  • During release review, warnings are tolerated, but Release Management may still ask for fixes.

Supporting resources

For documentation & training, please see:

For questions or comments, please use one of the following contact channels:

 

Special cudos to Herbert and Rafal for the hard work and many thanks to all people that made this possible 🙂 !

 

The CAMARA Release Management team

Fall26 (Sync26)

2026-02-23 Sync26 M0 announcement (former Fall26)

To: All, Codeowners; CC: TSC

Dear all,

Today we are happy to announce the M0 of the Sync26 meta-release which is the first meta-release that

  • is supported by the automated release process based on release-plan.yaml

  • will use the new meta-release naming: Synch26 instead of Fall26

The release automation rollout will starting this week:

  • first, a new PR “[Bulk] Add release-plan.yaml“ will appear (automatically) in each API repository.

    • it contains information on what to do to with this PR.

    • the release-plan.yaml replaces the API Release Tracker on the wiki.

    • codeowners may use this PR to update release-plan.yamlto reflect the team’s current release intent.

      • Note: if later changes are needed, updaterelease-plan.yaml anytime via usual PR(s) to main.

  • an information session is planned for March 05, 15-16h UTC to explain how to use the new release process

  • the new release process is documented here.

  • in the mean time, any questions can be addressed to the Release Management team on Zulip here: #camara-wg-release-management > Support for release automation rollout

 

The new meta-release naming is SignalYY/SyncYY as agreed by CAMARA Marketing:

  • Signal indicates the start of a new baseline for Commonalities and ICM, possibly also of new APIs

  • Sync indicates alignment and focuses on APIs

Signal/Sync replaces the previous Spring/Fall meta-release naming.

Going forward, we will now use the name Sync26 meta-release instead of Fall26

  • Note: In the near term, both names may still be encountered/used interchangeably. In particular, during rollout, both Fall26 and Sync26 may appear in release-plan.yaml; both are valid while we transition.

 

Have fun with automation for Sync26   

The Release Management team

Spring26

2026-02-20 Spring26 meta-release M2 announcement

To: Codeowners; CC: TSC

Hi all,

The TSC of February 19 has declared the M2 milestone for the Spring26 meta-release.

For the Spring26 APIs, please update your repositories as needed to align with the Spring26 Commonalities and ICM release candidates (linked above).

Please target to issue your aligned API M3 release PRs by February 28.

thanks for the hard work by all the teams 😊

Let’s go for Spring26 APIs !!

The CAMARA Release Management team

 

Fall25

2025-09-23: Fall25 meta-release announcement

Dear all,

 We are happy to announce that the CAMARA Fall25 meta-release is now available. 

The M4 and M5 milestones were declared by TSC on 2025-09-18.

This meta-release has 60 APIs in 40 repositories:

  • 10 stable

  • 23 new APIs

    27 updated APIs from Spring25. 

For more information, the full list of APIs and access to the releases, go here:

To learn about the market deployment of the CAMARA APIs, check-out here: GSMA Open Gateway Portal.

The first public announcement about the Fall25 meta-release is planned to happen in a webinar organized by CAMARA marketing on 2025-10-09

Announcements/presentations at many further API related events are being planned.

Please spread the word to your developer friends.

Happy hacking

The CAMARA Release Management team

 

Dear all,

We are happy to announce that the CAMARA Fall25 meta-release is now available. 

The M4 and M5 milestones were declared by the TSC on September 18th.

 The first public announcement is planned in a CAMARA webinar on October 9th.

 The Fall25 meta-release has 60 APIs in 40 repositories:

  • 10 stable APIs

  • 27 updated APIs from Spring25

  • 23 new APIs

 For more information, the full list of APIs and access to their releases, go here:

 A big thanks to all the teams for their great work and timely delivery.

 Please spread the word to your developer friends.

 Happy hacking

The CAMARA Release Management team

 

2025-08-22 Fall25 M4 call for PRs

To: Codeowners; CC: TSC

Hi all,

A gentle reminder that the cut-off date for the Fall25 public release PRs for review by Release Management is Friday August 29th.

Therefore if you have not done so already, please prepare your M4 release PR:

We will start with the reviews soon (to provide feedback on the available release PRs), but will provide final approvals only after the cut-off date.

/LGTM4

Many thanks from Release Management

 

2025-08-01 Fall25 M3 milestone reached

To: Codeowners; CC: TSC

Hi all,

The Release Management team is happy to announce that the M3 milestone for Fall25 has been reached today. The Fall25 plan is updated with the actual M3 date.

The “API harvest” is as follows:

Next steps: M4

  • Aug 15: public releases of ICM and Commonalities available

  • Aug 31: cut-off date for public release PRs of all Fall25 APIs

    • API implementation testing happens between M3 and M4 to harden the API - especially for stable APIs !!

    • before the M4 release PR, testing may lead to PRs to fix bugs in the API (please use dedicated PRs for such fixes)

Thanks a lot for all the hard work to meet the M3 milestone, both to API teams and to the Release Management reviewers.

/LGTM4

Many thanks from Release Management

 

2025-06-19 Fall25 meta-release M2 / M3 update

To: Codeowners; CC: TSC

Hi all,

The TSC of June 19 has declared the M2 milestone for the Fall25 meta-release.

 

The TSC has also decided to add one more week for the M3 milestone, so the new date is June 28.

  • June 28 is the cut-off data for the API release PRs to be submitted to Release Management for review

thanks for all the hard work by all the teams 😊

 

APIs, let’s go for Fall25 !!

The CAMARA Release Management team

 

2025-04-03 Fall25 meta-release kick-off (M0)

To: all@lists.camaraproject.org

Hi all,

We are pleased to announce that the TSC declared the kick-off (M0) of the Fall25 meta-release in their April 3rd meeting. (see minutes here).

The meta-release plan can be found here: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/36241429

M1 (tentatively shifts to April 29)

  • The proposal to shift the date to April 29 was supported by TSC members present, but due to lack of quorum, the official decision will be done in the TSC on April 17.

  • Commonalities and Identity & Consent Management

    • The scope issues with the Fall25 content are available on the meta-release page

    • Teams are preparing their alpha release for M1, trying as much as possible to avoid any breaking changes for the Fall25 meta-release.

  • AIl Sub Projects can start creating their API release trackers

  • Release Management prepares updates based on feedback concerning the following:

    • guidelines for versioning in notification URLs (update to Commonalities API design guidelines)

    • continuous numbering of pre-releases in the same meta-release to avoid number clashes in the API url field.

    • additional checklist item: API description for the marketing website

For questions or comments, please use the GitHub issues, the FAQ or email the wg-release-management@lists.camaraproject.org.

 

Let’s go for Fall25 !!

The CAMARA Release Management team

 

Spring25

2025-04-01: Spring25 meta-release: M6 announcement

To: codeowners@lists.camaraproject.org

CC: wg-release-management@lists.camaraproject.org

Hi all,

The Release Management team announced the M6 milestone which closes the Spring25 meta-release on April 1st (no joke 😊).

Please note that

For questions or comments, please use the GitHub issues, the FAQ or email the wg-release-management@lists.camaraproject.org.

Thanks for all the hard work for Spring25 !! 😊

The Release Management team

 

2024-11-08: Spring25 meta-release: M1 announcement

To: codeowners@lists.camaraproject.org

CC: tsc@lists.camaraproject.org, wg-release-management@lists.camaraproject.org

Dear CodeOwners,,

The Release Management team is happy to announce that the TSC has declared the M1 milestone for the Spring25 meta-release.

All API Sub Projects that want to participate in the Spring25 meta-release please:

  1. create a new API release tracker for each API version using the “Add API release tracker” button (do not copy previous release trackers as the format has changed). (Button: Go to your wiki home page → go to the API Release Tracking sub page, → hit the button).

  2. create the scope issue for this API version

  3. check the Commonalities and ICM scope issues and related release PRs to ensure alignment with their upcoming versions

  4. copy the new API readiness checklist for each APIs

  5. implement your API through alpha release as needed, and when ready, create the release PR for the first release candidate of the API anytime before for the M3 date (2024-12-21).

  6. request review of the release PR by the release Management team.

There will be an M1 update announcement as soon as Commonalities and ICM have created their alpha releases created.

At any time you can check the Spring25 meta-release plan to get the latest dates and links to Commonalities & ICM information.

All API Sub Projects that DO NOT want to participate in Spring25 meta-release please:

  • For Sandbox only APIs: apply above points 1 (change tracker page label to “camara-other”), 2, 3, and develop your API following the API release process.

  • For Fall25 APIs: apply above points 1 (change tracker page label to “camara-fall25”), 2, 3 and develop your API following the API release process.

This gives visibility to all APIs through the Wiki here: CAMARA meta-releases.

!! happy end-of-year coding !!

The Release Management team

 

2024-10-09: Spring25 meta-release: M0 announcement (all@lists.camaraproject.org)

We are pleased to announce that the TSC has declared the kick-off (M0) of the Spring25 meta-release in their October 3rd meeting.

 The meta-release plan can be found here: Meta-release Spring25.

 For M1 (Oct 31st), the Commonalities and Identity & Consent Management teams are working hard on their scope definitions:

  • The set of related PRs are under preparation: critical PRs will be available by Oct 15th and other PRs by Oct 31st.

  • Exceptionally, no pre-releases will be available yet for M1, so Sub-Project teams are asked to review and comment the PRs and start taking them into account as of M1.

 For questions or comments, please use the GitHub issues, the FAQ or email the wg-release-management@lists.camaraproject.org.

 All teams off to Spring25 😊

The CAMARA Release Management team

Fall24

2024-07-19: M3 milestone - new date: 2024-07-26 & preparation hints (to rm mailing list)

Dear all,

In the light of the upcoming M3 milestone, please find the following point to get prepared:

  •  

    the TSC has shifted the M3 date to 2024-07-26, but earlier is very welcome

  • at this date it is sufficient to have the release PR for the API release-candidate.

    • please put the link to the release PR in the (pre)-release tag field on the API release tracker when your PR is ready for review

  • in this release PR you need to include:

    • any updates to the readme.md as needed

    • the update of the changelog.md file

      • see example here: ReleaseManagement/documentation/CHANGELOG_EXAMPLE.md

      • HINT: create a "draft release" with GitHub to see the relevant changes since the previous version and select relevant PRs, reformulate as needed and sort them into the categories of the changelog.

    • the update of the yaml file with the concerned API version and URL

      • A reminder that the API version (x-y-z-rc.1) is different from the release number of the pre-release (which will be r1.1).  

    • the update of the API readiness checklist with all required content for the release-candidate

    • exceptionally, although the checklist mandates to provide the basic test cases with the release-candidate, for this first meta-release, the Sub Projects are allowed to delay these to M4. However the earlier the test cases are provided, the longer the time to actuall test any available API implementation. Please use the comment field in the checklist to indicate the delay if any. M3 will not be blocked on this point.

  • do not use release branches anymore: all releases are to happen using the GitHub release feature from the main branch and setting release tags on the main branch. If this is an issue for M3, this can be resolved for M4. 

  • please notify the Release Management team to review the PR by adding https://github.com/orgs/camaraproject/teams/release-management_maintainers as reviewers to the release PR. 

Other HINTS: (see API guidelines section 11.1)

 

  • check that your servers object in the yaml looks as follows:

servers:

  - url: '{apiRoot}/yourapiname/v0.yrc1 or v1rc1'

    variables:

      apiRoot:

        default: http://localhost:9091

        description: API root, defined by the service provider, e.g. `api.example.com` or `api.example.com/somepath`

 

  • add the following in the yaml in the info object: x-camara-commonalities: 0.4.0

example:

info:

  title: One Time Password SMS

  description: |-

    Service Enabling Network Function API to send short-lived OTPs (one time passwords) to a phone number via SMS and validate it afterwards, in order to verify the phone number as a proof of possession.

 

    # Relevant  Definitions and concepts

    - **NaaS**: *Network-as-a-Service* model where Telco Network resources are exposed to third parties through APIs. In this particular API, One Time Password is exposed following this model.

    - **OTP**: *One Time password* is a one-time authorization code (OTAC) that is valid for only one login session or transaction.

 

    # API Functionality

    It enables a Service Provider (SP) to send an OTP code by SMS and validate it to verify the phone number (MSISDN) as a proof of possession.

 

    # Resources and Operations overview

    This API currently provides two endpoints, one to send an OTP to a given phone number and another to validate the code received as input.

 

    # Authorization and authentication

    [Camara Security and Interoperability Profile](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-Security-Interoperability.md) provides details on how a client requests an access token.

 

    Which specific authorization flows are to be used will be determined during onboarding process, happening between the API Client and the Telco Operator exposing the API, taking into account the declared purpose for accessing the API, while also being subject to the prevailing legal framework dictated by local legislation.

 

    It is important to remark that in cases where personal user data is processed by the API, and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of 3-legged access tokens becomes mandatory. This measure ensures that the API remains in strict compliance with user privacy preferences and regulatory obligations, upholding the principles of transparency and user-centric data control.

 

  version: 1.0.0-rc.1

  x-camara-commonalities: 0.4.0

  termsOfService: http://example.com/terms/

  contact:

    name: API Support

    url: http://www.example.com/support

    email: support@example.com

  license:

    name: Apache 2.0

    url: https://www.apache.org/licenses/LICENSE-2.0.html

 

 

For more examples please see OTPvalidation and QualityOnDemand Sub Projects

Questions or comments ? create a Release Mgmt issue, mail the RM mailing list or look at the FAQ.

The links to the latter 2, and more generally on the API release process, are on the RM wiki and in GitHub.

Thanks !

The CAMARA Release Management team

 

2024-07-04: Meta-release M2: release PRs for Commonalities and Identity and Consent Management (tsc@lists.camaraproject.org)

Dear TSC members,

Dear TSC members

Please review the following 2 release PRs in preparation of the M2 milestone: