Release Planning

[FabrizioMoggio]

• update the API according to Fall25 Guidelines
• alpha release for Fall25 (0.4.0-alpha.1)
• improve the release if required
• Prepare the final PR for M3 (June 21) asking for review by the RM team (v0.4.0-rc.1)
• Review by RM team and bug fixing by the WG
• Merge final Release Candidate PR
• Create r1.2 Release Tag for Release Candidate
• Update the M3 date in the API Release Tracker (PR merged)
• Create a new WIP addressing further issues
• Final M4 PR for a public release at least moving the version from RC to Public before M4 (August 31)
• Merge final M4 PR (by August 31)
• Create the Release Tag for Public Release

[FabrizioMoggio]

Review here: camaraproject/ReleaseManagement#233

[FabrizioMoggio]

M3 is closed, please have a final look to the API for M4. Let's say for August 27th.

[FabrizioMoggio]

Because of #195, an update to the changelog is needed so a new RC must be created when the current wip is consolidated.