Scope for potential patch release r1.3 (v0.11.1/v0.1.1)

[hdamker]

Problem description

Some smaller issues were identified with the public release r1.2 within the meta-release. It is not yet decided if and when such patch release will be created, but it has to be

Expected action

Issues to be included if a patch release will be created:

• Authorization and Authentication section need to be aligned with ICM 0.2.0 text. #361
• Add user story for QoS Profile #341 (PR Add QoS Profile User Story #367)

Further issues to be considered:

• Support of Multi-SIM lines in QoD APIs #362
  • documentation of expected behaviour only, API changes within patch release
• Add explanation on why there is a "POST /retrieve-sessions" instead of GET #359
  • clarification in documentation only

To be addressed when creating the patch release:

• Local links within API documentation have to be release specific #363 (to be addressed within the release PR)

Additional context

[jlurien]

Regarding #362

• documentation of expected behaviour only, API changes within patch release

Risk here is that in absence of guidelines in current release, some early implementation had taken its own decision, and if we give now some guideline in other direction, that would make those early implementations incompatible with the new patch. On the other hand, if we keep the gap, the risk of implementations having different behaviour for the same input is also there.

[RandyLevensalor]

A decision was not made, but it seems likely that #362 will not be included in this patch release. This will be discussed further once a PR is available to review to impact of the change.