2025-10-21 Release WG Minutes
Community Attendees:
@Herbert Damker @Tanja de Groot
Community Attendees:
@Alberto Ramos Monaga
LF Staff:
@Casey Cain
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: no comments, approved
Action Items Review
See action items list here: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14552660
RM issue #327 on use of milestones
usage to be documented, check with ICM to align on the same
possibly apply the same to all the APIs (to be discussed).@Tanja de Groot to create an issue for this
if applicable to APIs, some milestone naming rules need to be provided by Release Management team
should allow to check progress automatically
need to check how to manage the review status tacked/updated in the new approach - add to the wish list on Wike of things to automate @Tanja de Groot
@Herbert Damker to create an issue in governance to ask for review of the two new timeline pages and remind TSC of the review.
Linting rollout is done - PRs are in the API repos.
Do we check if done ? yes @Herbert Damker to create an issue to check next week the status of the PRs (merged or not).
@Herbert Damker to provide this status for next week's meeting.
issue on API description link: @Tanja de Groot to put it in the wish list for automation - should point to the API description on the camara website:
link to automation wish list wiki page: Release PR checks (Commonalities)
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 has been released (r3.1)
can we declare M6 with this ? or should we wait until the process documentation is updated ?
we declared M6 milestone for the Fall25 meta-release today by Release Management
the changes to the process documentation for the new meta-release schedule will part of Spring26 preparation.
updated the Release management home page with the link and date to the release r3.1
Updated the info on the Release Management home page and the https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14574702 (source) page with a new (but manual) way to represent the list of meta-releases.
@Tanja de Groot to update the https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/36012257 page:
rename to “Sandbox APIs outside meta-releases”
have 2 lists: released APIs, APIs under development (wip)
ensure the data can be pulled with the automation flows by Herbert
looking for a way to “tag” the confluence before starting the process updates.
Herbert suggests to use a comment to add a “tag” which will show on the page history.
@Tanja de Groot to check which pages to tag, if not all.
next steps: confluence and GitHub documentation to be updated
Spring26 meta-release (https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/268500993 )
M0
M0 was declared on Oct 2nd in the TSC meeting. See 2025-10-02 TSC Minutes - CAMARA Project - CAMARA Project
M1 schedule
The M1 date in the new preliminary schedule is nov 30 (see https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/268500993 )
Note: APIs are recommended to target the Fall26 Meta-release, but some exceptions can be discussed.
For these exception, the concerned APIs should be aware that the Spring26 schedule is very tight.
Release Management 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 the new approach and what the API Sub Projects need to do
M1 Commonalities & ICM
Commonalities and ICM are preparing content for Spring26
Commonalities Spring26 scope issue: Scope of the Spring release #543
ICM Spring26 scope issue: ICM scope for the Spring26 meta-release #311
M1 APIs (Spring26 is optional for initial APIs)
Recommended approach to be described for APIs
M2
Target date is Jan 31, 2026 for the release-candidate of Commonalities & ICM.
Release schedule update
New meta-release schedule proposal following the feedback in Dual Phase proposal.
Release Management proposal was presented to TSC on oct 16.
TSC decided to put the proposal as preliminary new schedules on the wiki. See
These pages are open for review until the TSC of Nov 6th
@Herbert Damker to send a reminder to TSC and an issue in Governance for the same
New meta-release naming : please check & comment
Meta-Release Naming — Community Discussion · Issue #200 · camaraproject/Governance .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 - done - issue created: Meta-release naming - community discussion · Issue #40 · camaraproject/Marketing
Issues review - Release Management
See Issues · camaraproject/ReleaseManagement - progress is logged in the issues
review done - status quo
Issues review - CAMARA Project Administration (repository)
repository link: project-administration
2 open issue
new issue to be done by @Herbert Damker to link the PR for an update of the bulk change work flows (to handle e.g. “back to wip”)
AOB
none