Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff: Casey Cain
Community: Herbert Damker Jan Friman Sachin kumar Tanja de Groot Ludovic Robert Mark Cornall Samuel Adeyemo
Agenda
The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF. |
- Roll Call
- Action Items Review
- progress
- Agenda Bashing
- General Topics
- Any Other Topics
Minutes
- Nokia (Tanja de Groot) nominated
- Release management manager (Define list of maintainers for ReleaseManagement · Issue #1 · camaraproject/ReleaseManagement (github.com))
- Tanja mentioned that Nokia organization is willing to nominate Samuel Adeyemo to act as Release manager (see https://lists.camaraproject.org/g/release/message/7)
- 2 is the minimum but we can have more than 2 release manager.
- Release manager report to TSC about release progress
- Casey reminded to the team that training course are available here:
- Herbert raised the 'current' urgent issue for CAMARA about 'meta/wide-release' management
- We need to provide to each project guidance about practically how to version/name the release
- Consolidation of Release issue is listed here Consolidation Issue for open points release management · Issue #9 · camaraproject/ReleaseManagement (github.com)
- Discussion how we can spread the work between release management project and commonalities one (to update documentation in guideline document)
- Meta/wide CAMARA release is more coordination of snapshot of all CAMARA projects
- Discussion about definition of the readiness to make a release (minimum of implementation, sandbox, alignement with test definition, etc.)
- Discussion of the management of the API Family - Does we need to have a family versioning and how it is reflected in the yaml?
- Following London meeting we have the 'family' version in the API path but also the API (yaml) version in the info (see device location for example)
- Tanja mentioned that there is some dependency between API and Family but at the end of the day the developers care about yaml definition
- We need to document how we manage working group release version vs api version
- Discussion about alignement between commonalities version and api for a meta/wide release
- Linting could be helpful to check API conformance to commonalities rule
- It is valid to have an API not updated to latest guidelines and not part of a release → this should be discussed/handled in TSC