Release Review: NetworkSliceBooking r2.2 (rc Spring26)

[camara-release-automation]

Release Review: r2.2 rc

This PR finalizes the reviewable release content for the active snapshot.

Edit and review this PR before merging it into the release snapshot. After Codeowner and Release Management approval, merging this PR creates the draft release.

Release contents

API	Version	Status
network-slice-booking	0.2.0-rc.2	rc
network-slice-assignment	0.1.0-rc.2	rc

Dependencies: Commonalities r4.2, ICM r4.2

Codeowner Actions

1. Update release notes

• CHANGELOG updated: copy all API-consumer-relevant changes into the appropriate Added / Changed / Fixed / Removed sections for each API as needed.
  Do not copy administrative, tooling-only, or internal maintenance changes unless they affect API consumers.

2. Confirm API release readiness

• API version(s) used in all files match release-plan.yaml
• API definitions comply with declared Commonalities version
• API documentation is complete
• Basic test cases are present (sunny day + main error cases)

Release Management Actions

• CHANGELOG follows the release documentation rules
• Breaking changes are documented and version updates follow SemVer rules
• Mandatory release assets are present for each API according to its status

Required release assets per API status

Nr	Asset	alpha	rc	initial public	stable public
1	Release Plan	M	M	M	M
2	API Definition(s)	M	M	M	M
3	Commonalities compliance	O	M	M	M
4	API Documentation	M	M	M	M
5	User Stories	O	O	O	M
6	Test Cases (basic)	O	M	M	M
7	Test Cases (enhanced)	O	O	O	M
8	API Description	O	O	M	M

M = Mandatory, O = Optional — Full documentation

During the automation introduction phase, please also verify the snapshot content: that release-metadata.yaml is correct, that the generated API version numbers and server URLs (and other version fields and references) are right, and that the README update reflects the release tag and version handling.

Valid next actions for codeowners

• Merge this PR when all Codeowner Actions and Release Management Actions are complete and the required approvals are present — creates the draft release
• Use /discard-snapshot <reason> in the Release Issue to discard this snapshot, return to planned, and update content on main

---

Snapshot: r2.2-a4d3418

[camara-validation]

CAMARA Validation — PASS

0 errors, 2 warnings, 12 hints | Profile: standard

View full results

[tanjadegroot]

almost there. two small fixes in the CHANGELOG part which you can apply in this PR

[tanjadegroot]

you need to complete the dots, e.g.

"... is the second release-candidate of the Network Slice Booking API to align with Commonalities r4.2."

[tanjadegroot]

same comment: need to complete the dots, e.g.

"... is the second release-candidate of the Network Slice Assignment API to align with Commonalities r4.2."

[tanjadegroot]

Hi Team,

On the 2 remaining warnings (DateTime-2): you would either

• need to change the name of the schema to respect PascalCase (which does not allow dashes "-"), e.g. DateTime2
• remove this schema as it seems exactly the same as the CAMARA_common.yaml schema.

I think the copy of the DateTime schema you have in your API file is outdated as it has an additional WARN: ... line which has been removed in the latest Commonalities version.

So it seem that you can safely remove the DateTime-2 schema and always reference DateTime.

FIY please note that such issues can be avoided in the future by adopting the bundling functionality of automation:
To do that you would

• remove all common schemas from your API file
• replace all references to these schemas by an external reference as follows, e.g.:
  • use $ref: "CAMARA_common.yaml#/components/schemas/DateTime"
  • instead of $ref: "#/components/schemas/DateTime"

or

• use $ref: "CAMARA_event_common.yaml#/components/schemas/Source"
• instead of $ref: "#/components/schemas/Source"

Release 2.2 options

There are now 2 options:

1. either you fix these 2 warnings now (/remove-snapshot > fix on main > /create_snapshot > copy changelog/readme updates kept on the xxx-preserved branch back into the release review PR)
2. create a new issue to fix these warnings for a later release and go to release with this one

I would recommend that you do these changes in a later release in which you may then also decide to introduce the external references to the CAMARA common files, as recommended (but not yet mandatory) for Spring26 based APIs.

if you chose option 2, the only thing left now is to fix the CHANGELOG, to merge the Release Review PR after approval, and then release r2.2.

[XunliYang]

Hi @tanjadegroot , thanks for the suggestions. The fix of CHANGELOG has been done. Besides, I see that these two warnings like DateTime-2 and Source definitions did not occur in main branch. I don't know how it comes in this branch (also confused :).
By the way, option2 looks better to me.

[tanjadegroot]

Hi @tanjadegroot , thanks for the suggestions. The fix of CHANGELOG has been done. Besides, I see that these two warnings like DateTime-2 and Source definitions did not occur in main branch. I don't know how it comes in this branch (also confused :). By the way, option2 looks better to me.

Thanks @XunliYang for the updates. Let's go forward with option 2 and publication :-)

If you can please create a new issue to address the warning and Hints where applicable for the next release, and to remove the DateTime-2 schema as well.

@hdamker you may want to check why the PascalCase warning did not show up in the main branch PR validation.

[tanjadegroot]

All good, thanks !
/LGTM from Release Management

[hdamker]

If you can please create a new issue to address the warning and Hints where applicable for the next release, and to remove the DateTime-2 schema as well.

@hdamker you may want to check why the PascalCase warning did not show up in the main branch PR validation.

I created #124 with the explanation of the issue and the fix.