Scope of QoS B v0.2.0 and QoS B&A v0.2.0

[Masa8106]

Problem description

This issue describes the scope for the next version of QoS Booking API and QoS Booking and Assignment API.
The Spring26 meta-release is an optional release for initail APIs. So we need to decide whether the next version of our APIs target to Spring26 meta-release or not. (If yes, we needs to submit an issue in Release Management to request Spring26 participation by Dec 15.)
The issue description will be regularly updated based on opened issues.

Expected action

Target of the next version (Spring 26, Fall26 or independent release?)

• QoS Booking API:
• QoS Booking and Assignment API:

Target versions

• QoS Booking API: v0.2.0
• QoS Booking and Assignment API: v0.2.0

Issues to be addressed in the next release's scope

QoS Booking API v0.2.0

• Enhance the quality and deep of QoS Booking tests #69
• QoS B: Update the status diagram #83
• QoS B: Alignment with Commonalities r4.1 #84 (will be implemented at M3 or M4)

QoS Booking and Assignment API v0.2.0

• Error handling when assignment is requested at incorrect time #62 (will be implemented at at M3 or M4 due to one of commonalities issue)
• qos-booking-and-assignment : Appropriate success codes should be returned #64
• Updates to align with Spring26 Commonalities (will be implemented at at M3 or M4)

Backlog: Further Issues under discussion

QoS Booking API v0.2.0

• QoS B: update of request parameter for serviceArea #86

QoS Booking and Assignment API v0.2.0

• qos-booking-and-assignment: release end point must support both sync and async operations #63
• qos-booking-and-assignment: An end-point to get the current state of the given device in the context of a booking #65
• qos-booking-and-assignment:A new endpoint to extend (or reduce) the duration of a booking #66
• qos-booking-and-assignment: A new endpoint needed to modify device count in an active booking #67
• qos-booking-and-assignment: A new endpoint needed to check QoS availability #68

Additional context

None

[Masa8106]

My proposal on the target of QoS Booking next version is the independent release in 26Q1.

[RamTMO]

#62 #63 #64 #65 is in plan. Depending on how the state management goes we can evaluate 66,67 and 68. Let us discuss in the next meeting.

[Masa8106]

Hi, @RamTMO ,

There is the following text in the last meeting minutes: QoSBooking - independent release in Q1 2026, based on Fall25 commonalities or already on Spring26 (still to be clarified, depends on time of actual release, see
Spring26 meta-release | Spring26/Fall26 guidance for API release planning)

My preference is to set 2nd half of March to the planned release date and to make the next version be based on Spring26 commonalities. What do you think about it?

[Masa8106]

Hi, @RamTMO and @jlurien
As I mentioned in the last call, I believe it is good for us to release the next version, v0.2.0, which will be aligned with Spring26 commonalities, as an independent release in 2nd half of March, because I think this would be a milestone for Fall26 Meta release.
If any, I welcome with your feedback. Thank you.

[Masa8106]

Hi, @gmuratk (@jlurien)
M1 date for Sync26 (ex-Fall25) meta-release (30th April) is approaching now. I will open an alpha release PR in 30th April.
So would you confirm issues to be addressed in the next release's scope for QoS B&A API, which are issues having already assosicated PRs? Thank you.