Community Attendees:
Community Attendees:
LF Staff:
Agenda
DRAFT
Antitrust Policy
- Agenda Review
- Action Items Review: Release Management Working Group - CAMARA Project - Confluence
- Open Issues Review: Issues · camaraproject/ReleaseManagement (github.com)
- Meta-release status: Meta-release Fall24 - CAMARA Project - Confluence
- API reviews - practicalities
- FAQ
- Vacation schedule (reminder)
Minutes
Action Items Review
- Missing release manager will handicap M3 milestone reveiws
Open Issues Review
Add team release-management_maintainers to all sub project with read access in order to allow Sub Projects to mention the team wg management
#43 opened 18 hours ago by hdamker
Clarification on release tag and version naming for Commonalities and ICM documentation
#41 opened last week by rartych
Update links in README.md file documentation
#40 opened 3 weeks ago by tanjadegroot
API Versioning - Aggregation backlog question release management
#14 opened on Jul 6, 2023 by chrishowell
Meta-release status
- 23 APIs (+2). 3 stable APIs
M3 API reviews - practicalities
- how to distribute work - proposal to use a Sub Project issue in which to track what is reviewed and by whom ?
- make checklist for Release Managers to put in that issue
- RM issues in which Sub Projects can reference their review issue / release PR ?
- other ?
- question: would it make sense/allowed to have an additional release of the same API version in case of RM reveiw updates for example or do we need to increase the version number in all cases ?
FAQ
What to do if I accidentally released my API before Release Management check ?
You can easily create a next release rx.y+1 at any time.
In this case, create a "Release Management review" issue in your Sub Project and assign it to a release manager (tbc)
If there is a change required, this will be put in the comments in the issue and the Sub Project team can start a new PR to include the changes.
The Sub Project can decide when to merge the PR and create the new release. If it concerns changes to the API yaml file, then also the API version should be increased in-line with the type of change (most likely MINOR ot PATCH).
Vacation schedule:
- Samuel: 2 weeks in August
- Tanja: Aug 5-30th
- Rafal: Aug 12-16 + other tbd
- Casey: first week of Sep
- Herbert: tbc