...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Attendees & Representation
...
- Commonalities and ICM release candidates available
- All Sub Projects are asked to prepare for the meta-release, including creating API release trackers for their APIs under their wiki pages, preparing their release-candidate API version and their API readiness checklist items.
- Target: First release-candidates of API Sub Projects to be provided by 07-21
Open Pull Requests (open for review)
- PR #306 Add HTTP-status-codes for better Error Handling
- After discussion reduced to add HTTP-status-code 429
- Supersedes also the (draft) PR #297 Add error 429 QUOTA_EXCEEDED?
- Jose Luis Urien Pinedo will do a cross-check of the PR, also with other APIs like DeviceLocation
- Target to get it close within next week
- PR #318 Add query to qos-profiles to query profiles available on a given device
- Addresses #166
- Open question: one endpoint for all cases?
- no objections to go with one POST endpoint
- Randy Levensalor will update the PR
- PR #299 New API QOD Provision
- Name of API changed to qod-provisioning
- Request to all to review the latest version within the Pull Request. Please add your comments (or approval) until end of next weeks
- PR #320 New API Readiness Checklists for quality-on-demand and qos-profiles
- Created and prefilled to check the current status
- Need to be updated as part of each release PR
...
- #322 Remove cucumber code from the repository - decision request
- no objection to delete the code => PR to be created
Issues relevant for v0.11.0 (if not yet covered by PRs)
...
- PR #320 New API Readiness Checklists for quality-on-demand and qos-profiles
- Current open "to be dones":
- API Definition (open Issues/PRs)
- DesignguidelinesfromCommonalitiesapplied (open Issues/PRs)
- BasicAPItestcases & documentation (see #245!)
- Changelog update (will be done in release PR)
- User stories and Enhanced API test cases are not mandatory for 0.x API versions
- Current open "to be dones":
- Target to have the release candidate PR ready within the next QoD call on July 26th.
- 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 July 26th, at 14:00 CEST / 12:00 UTC
- We don't plan to skip meetings until the release (at least for now).
...