Spring26 meta-release time plan

[rartych]

Initial proposal - https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/252772353/v2+Updated+meta-release+plan#Transition-period

• M1 (alpha) : Nov 30
• M2 (release candidate): Jan 31
• M4 (public): Apr 15

Considering that Release PR should be ready for review around 2 weeks earlier we get:

• PR for M1 (alpha) : Nov 15
• PR for M2 (release candidate): Jan 15
• PR for M4 (public): Apr 1

I think in order to have more complete content (all major changes included) of alpha release M1 should be shifted later (like Dec 15).

[PedroDiez]

Hi,

@rartych, thanks for bringing up and sharing the inital timeline.

I share the same feedling about to delay M1 in order to have more consolidated content

[rartych]

As I mentioned in the call and Release Management accepted the proposal to make M1 optional in this transition period.
https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/259784767/2025-10-14+Release+WG+Minutes
I think we can keep M1 internally in Commonalities to track the progress (without effort on alpha release preparation) and then target to be ready with PR for M2 (release candidate) in Jan 15.

[tanjadegroot]

@rafal: please note that in the final meta-release timelines the M4 date is March 15, not April 15.
You may want to update this discussion as it is referred to from the Spring26 scope issue.

The link in this discussion refers to an old page, please refer to the following:

• Spring26 meta-release
• Fall26 meta-release