DRAFT MINUTES
Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff:
Community:
Agenda
- Antitrust Policy
- Review of previous meeting minutes
- Overall Topics
- Regular Topics
- Open Pull Requests
- New Issues
- Issues relevant for v0.11.0
- Any Other Topics
Minutes
Review of previous meeting minutes
- Previous meeting minutes: 2024-07-12 Quality on Demand - Meeting Minutes
- no comments
Overall topics
- Target: PR for release-candidates of API Sub Projects to be provided by 07-26
- Current status:
Open Pull Requests (open for review)
- PR #327 Update ICM AuthZ/AuthN Template to Release 0.2.0 wording
- ...
- PR #325 List sessions endpoint for quality-on-demand
- ...
- PR #326 Align quality-on-demand with Commonalties regarding optional device object and error message
- Only quality-on-demand yet (qos-profiles to be considered)
- ...
- PR #318 Add query to qos-profiles to query profiles available on a given device
- ...
- PR #299 New API QOD Provision
Closed issues
- #322 Remove cucumber code from the repository (with PR #323)
- #321 Remove unresolved reference within quality-on-demand documentation (with PR #324)
- #314 Adding
notificationUrl
as an optional property inCloudEvents
(closed as not planned) - #305 Add more HTTP Status Codes for improved Error Handling (with PR #306)
New Issues
Issues relevant for v0.11.0
- #245 Update and enhance test definition file for QOD API
- Jose Luis Urien Pinedo will check if internal test definitions can be adapted
- #313 Align with Commonality decision about optional device object and respective documentation
- Addressed in #326
- #315 Return 422 instead of 501 if the service is not implemented for specified device
- Addressed in #326
- #316 Align error responses for Device Object with v0.4.0 of Design Guidelines
- Addressed in #326
Review scope and time plan for Release Candidate
- #292 Scope of QualityOnDemand for Fall24 CAMARA release
- Review scope in light of short-term deadline
- We will go for the Meta-Release with an "Initial" API Version, which means to keep v0.11.0
- Why we don't go for "Stable":
- Lack of prerequisites (test cases, certification of previous version)
- Too many changes between v0.10.0 and v0.11.0, we should have one cycle where we don't introduce breaking changes
- Why we don't go for "Stable":
Any other topics
- Next QoD meeting will be on August 9th, at 14:00 CEST / 12:00 UTC
- We don't plan to skip meetings until the release (at least for now).