Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DRAFT

...

MINUTES

Attendees & Representation

...

  • PR #299 New API QOD Provision
    • Name of
    • endpoint to be discussed (see comments from Randy Levensalor within the PR). Eric: "provision" is mobile terminology, would be good to avoid.
    • 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
    • Jorge Garcia Hospital will ask Jose Luis Urien to address the comments.
    • To be able to include it within the release candidate we need to conclude the discussions about the PR until the next meeting (starting the final review).

...

Review scope and time plan for Release Candidate

...

  • 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
  • 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

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).

...