Prepare release r1.1

[hdamker]

What type of PR is this?

Add one of the following kinds:

• subproject management

What this PR does / why we need it:

Prepare the release r1.1:

• Update CHANGELOG.med
• Update README.md
• Set versions in quality-on-demand and qos-profiles
• Set version in qos-provisioning (check all "wip", including event version)
• Update API Readiness Checklists

Update - additional fixes

• Aligned sink description between quality-on-demand and qod-provisioning to address Remove reference to protocol in sink description #338

Which issue(s) this PR fixes:

Fixes #334 #338

Special notes for reviewers:

[hdamker]

@RandyLevensalor @jlurien have a look on the r1.1 section in CHANGELOG.md.

[hdamker]

Release PR is almost complete ... just waiting for the merge of #299 and the ability to set the version in the new API qos-provisioning to 0.1.0-rc.1

[hdamker]

Replaced all "wip" in qod-provisioning.yaml:

• in version and server field according to guidelines
• in org.camaraproject.qod-provisioning.vwip.status-changed to org.camaraproject.qod-provisioning.v0.status-changed. My thoughts here:
  • There is no specific guideline for initial API versions, but other initial APIs have used here also v0 (e.g. in DeviceStatus)
  • The event version should be decoupled from the API version (as the API can have breaking changes, but keep the event structure stable) ... so if the event structure will change in a further initial API version we can still then use another number.
  • BTW: I would not reset to wip as long as there is no breaking change to the event structure within a PR. I would anyway expect that it is more probably that the event type guideline will change than the event structure.
• in line 1087 ... set to the current base path v0.1, but it is only an example, wouldn't matter too much if we miss this one going forward

[hdamker]

@camaraproject/quality-on-demand_maintainers @camaraproject/release-management_maintainers
The release PR for r1.1 is now complete and ready for review.

Note: #325 has to be merged first before this PR can be merged and the release created.

[jlurien]

LGTM

[rartych]

LGTM

[RandyLevensalor]

LGTM