Spring25 - Planning

[FabrizioMoggio]

Considering:

https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14560849/Meta-release+Spring25
https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14551399/Meta-release+Process

List of the needed actions:

• Create Release Tracker
• Create a release PR according to the scope (Scope for Meta Release Spring 25 #114)
• Update Test Cases (at least for release number)
• Update Changelog
• Update Readme.md
• Update Readiness Checklist
• Consolidated WIP PR merged
• Prepare the final PR (with version number) for M3 (17th of January) asking for review by the RM team (version v1.0.0-rc.1 or v0.3.0-rc.1)
• Certification from GSMA to have a Stable Version
• Review by RM team and bug fixing by the WG
• Merge PR with Release Candidate
• Create r2.1 Release Tag for Release Candidate
• Update the M3 date in the API Release Tracker (PR merged)
• Final M4 PR according to internal review by the WG and potential fixing, at least moving from v0.3.0-rc.1 to v0.3.0 (by 24th of February)
• Merge final M4 PR (by 26th of February)
• Create r2.2 Release Tag for Public Release (by 28th of February)

[FabrizioMoggio]

Release Tracker: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/55607324/call-forwarding-signal+v1.0.0

[FabrizioMoggio]

Readiness Check List issue: #126
Readme issue: #127
Test Cases issue: #124
Change Log issue: #128
PR with reference to scope: #121

[FabrizioMoggio]

@bigludo7 , @chinaunicomyangfan , @StefanoFalsetto-CKHIOD the current merged PR is going to become v1.0.0-rc.1.

@StefanoFalsetto-CKHIOD when is it planned to have your implementation of the API certified by GSMA?

[FabrizioMoggio]

Considering: camaraproject/ReleaseManagement#134 (comment)

it was not required to update the M3 date on the Wiki API Tracker when the M3 RC PR was submitted. The M3 date must be updated when the PR is Merged after the Release Management Review.