Community Attendees:

@Ludovic Robert @Toshi Wakayama @Fernando Prado Cabrillo @Alberto Ramos Monaga

Community Attendees:

LF Staff:

Agenda

The project's Antitrust Policy is linked from the LF and project websites. The policy is important when multiple companies, including potential industry competitors, are participating in meetings. Please review it, and if you have any questions, please contact your company’s legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

• Release agenda update

• OTP

• SIM Swap

• Device Swap

• Number Verification

Minutes

Release agenda update

As of now the M3 was planned for Jul 8, 2025 but not yet reached - TSC this afternoon

Aa a reminder a Release Candidate PR must prepared & merged for M3

OTP Validation

• one-time-password-sms has no breaking change - It will be a patch release: from v1.1.0 to v1.1.1

  • No need for a M3 release candidate

  • We will go directly to the release

    • PR is ready (https://github.com/camaraproject/OTPValidation/pull/113 )

SIM Swap

• Release r3.1 PR is ready for merging (Prepare r3.1 by fernandopradocabrillo · Pull Request #226 · camaraproject/SimSwap)

  • it features:

    • sim-swap 2.1.0-rc.2

    • sim-swap-subscriptions 0.3.0-rc.1

  • Merged !

Device swap

• Release r3.1 PR is ready for merging (camaraproject/DeviceSwap: Incubating API repository for DeviceSwap API(s))

  • Last updated following Release Management Team review done (changed feature name)

  • it features:

    • device-swap v1.0.0-rc.1

• Request from TIM Brasil to add Device Swap Subscriptions API

  • OK from Backlog team

  • TIM Brazil is in UTC+3 so our meeting doesn't fit - we can have adhoc call → Any company interested by this API?

    • …

  • Proposal is to not target Fall25 because a bit late but we can work on this API to have a v0.1 in the coming weeks/month, make an independent release and then be part of Spring 26 CAMARA Release.  We have done this way for device swap itself.

Number Verification

• Before the release we have to merge the update Test plan (https://github.com/camaraproject/NumberVerification/pull/204 ) - done

• Then we have to focus on the PR for the release r3.1 (camaraproject/NumberVerification: Incubating API Repository for the NumberVerification API)

  • Probably some repo re-basing will be required.

  • Target API: number-verification 2.1.0-rc.1

• Issue 207 - Referenced UML content is not up-to-date

  • We can do it between M3 and M4

• Issue 205 - Remove AUTHENTICATION_REQUIRED error code (Remove AUTHENTICATION_REQUIRED error code · Issue #205 · camaraproject/NumberVerification)

  • This is part of PR#206