DRAFT AGENDA
...
- PR #325 List sessions endpoint for quality-on-demand
- PR #326 Align quality-on-demand with Commonalties regarding optional device object and error message
- #313 Align with Commonality decision about optional device object and respective documentation
- #315 Return 422 instead of 501 if the service is not implemented for specified device
- #316 Align error responses for Device Object with v0.4.0 of Design Guidelines
- ?? #328 Device in response object need to be omitted or clearer defined
- Is this issue completely addressed or only partly?
- PR #318 Add query to qos-profiles to query profiles available on a given device
- PR #299 New API QOD Provision
Open Pull Requests (open for review)
- #336
- #339
New Issues
Issues relevant for v0.11.0
- #245
- 337 ...
- Provide feedback
Issues
- #328
- Close and refer to Commonalities "API Misuse" for further discussion and potential changes.
- #245 Update and enhance test definition file for QOD API
- Jose Luis Urien Pinedo will check if internal test definitions can be adapted
- #317 contiune disucssion, potential enhancement for next release
Review scope and time plan for Release Candidate
- #292 Scope of QualityOnDemand for Fall24 CAMARA release
- Plan remaining task for public release of v0.11.0 & qod-provisioning
- Test definition files: see #245
- User Story
- qos-profiles Randy Levensalor
- quality-on-demand Herbert Damker
- 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 23rd, at 14:00 CEST / 12:00 UTC
...