2025-10-14 Release WG Minutes
Community Attendees:
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.
Action Items Review
Discussion Review
Fall25 meta-release
Spring26 meta-release
Release schedule update
Issues review - Release Management
Issues review - CAMARA Project Administration (repository)
AOB
Minutes
Approval of previous meeting’s minutes: approved
Action Items Review
See action items list here: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14552660
Scope issue and milestone feature: use github milestone feature to focus on internal Working Group delivery and dates, not meta-release milestone dates (e.g. the internal milestone dates would be generally 15 days before the meta-release milestone date).
linting rollout: wiki page and PR https://github.com/camaraproject/project-administration/pull/23 updated - ready for review
Discussions Review
See camaraproject/ReleaseManagement · Discussions · GitHub: No new discussion.
Fall25 meta-release (https://lf-camaraproject.atlassian.net/wiki/x/FQApAg?atlOrigin=eyJpIjoiZWIyZGY3YWY4Yzk2NGQxNWFjODlkZGNmYmFmYTVkMDIiLCJwIjoiYyJ9)
M6
release cycle cadence change proposal: see below section on Release schedule update
release-management repo release - Should be done before merge of any PR with changes for Spring26 … just to have checkpoint what was valid for Fall25 (comment from Herbert) - Agreed @Tanja de Groot to create the release PR and related info
Spring26 meta-release (https://lf-camaraproject.atlassian.net/wiki/x/AQB_Cg)
M0
M0 was declared in last week’s TSC meeting. See 2025-10-02 TSC Minutes - CAMARA Project - CAMARA Project
M1
delayed from Oct 15. alpha and release-candidate (M2) release dates to be determined.
Proposal from Commonalities to skip the alpha release and prepare the RC for Jan 31st (release PR for Jan 15th)
M1 is made optional for the transition period
Commonalities and ICM are preparing content for Spring26
scope issue links to be added
M1 APIs
Start API work against the Fall25 Commonalities (r3.4) and ICM (r3.3)
Do the scope definition
Define the release-plan.yaml file
RM to
roll out the release-plan.yaml files for the current API versions to API Sub Projects
update wiki / github API process
AHC in November: present what the API Sub Projects need to do
M2
Target date is Jan 31, 2026
Release schedule update
New meta-release schedule proposal following the feedback in Dual Phase proposal: see
THIRD DRAFT:
Steady state schedules and Spring26/Fall26 are proposed:
Release Management proposal for the steady state case is ready
Spring26 and Fall26 adjusted schedule for the transition period based on the following assumptions:
limited number of APIs to be release in Spring26, focus is on Comm/ICM releases.
initial APIs can create a release at any time and ask for review: they should use the Fall25 Comm/ICM release until the public version of Comm/ICM of Spring26 is available at M4 (Mar 15 2026)
Fall25 APIs should plan to prepare updates for Fall26 based on Comm/ICM of Spring26.
New meta-release naming : please check & comment https://github.com/camaraproject/Governance/issues/200 .
TSC - ask for resolution proposal e.g. a vote of top list - decision in the TSC after that.
Need to involve the marketing team @Tanja de Groot
Issues review - Release Management
See Issues · camaraproject/ReleaseManagement - progress is logged in the issues
not reviewed
Issues review - CAMARA Project Administration (repository)
repository link: project-administration
no new issues
AOB
N/A