Release 2.1 (Spring25 M3)

[hdamker]

What type of PR is this?

Add one of the following kinds:

• subproject management

What this PR does / why we need it:

Preparing all files for r2.1 with the release candidate versions for Spring25 M3 milestone.

Includes:

• Set the version with API and Test definition files
• Updated internal links to point to the right release
• Updated the API Readiness Checklists
• Added the pre-release to the README
• Updated the CHANGELOG

Current status:

• Ready for codeowner and release management review

Which issue(s) this PR fixes:

Fixes #397
Fixes #408

Special notes for reviewers:

Please check especially if the notes about breaking changes are complete or if there are additional points which should be mentioned here.

[hdamker]

@camaraproject/quality-on-demand_codeowners Updated the current status in the PR description, 3 PRs need still to be merged. But please start also to review the release PR so that we don't loose time.

My view on the open PRs:

• Add L4S/DSCP support to QoS Profile #384 - no changes or comments since last week, 2 approvals available, will merge tomorrow if there are no further comments
• Use common artifact for device test scenarios #400 - some fixes done by @eric-murray two days ago, will merge tomorrow if there are not further comments
• Adapt text on identifying devices from the access token for qos-profiles.yaml #410 - related updates of test cases to be done, then ready for final review

[hdamker]

Note added to PR description: "PR is already referring to r2.2 of Commonalities and ICM, so need to check for last minute updates in these releases."

[hdamker]

Added #412 to CHANGELOG and PR description.

[hdamker]

@camaraproject/quality-on-demand_maintainers @camaraproject/quality-on-demand_codeowners @camaraproject/release-management_maintainers

The release PR is ready for your (final) review. All relevant PRs are merged, I've also updated the "Authorization and authentication" section with the latest small change from ICM r2.2

[hdamker]

Ready here, but need to wait for a review from @camaraproject/release-management_maintainers.

[tanjadegroot]

Nearly there -

• some versions / links need to be updated
• some thoughts about the English in the qod-provisioning.yaml description fields

[tanjadegroot]

line 291: update the link to r2.2 or change link to point to the Commonalities repository, and give textual description of the location of the section in the API Guidelines.

[hdamker]

Changed short-term to r2.2 in 11d501e

[tanjadegroot]

RESOLVED

[tanjadegroot]

r2.2 or rather a local reference only "/documentation/API_documentation ...

Same change on line 87

[hdamker]

Both changed in 55e29d1

[tanjadegroot]

RESOLVED

[hdamker]

@tanjadegroot All review comments should been addressed above. Please have a look and mark the conversations as resolved if this is the case.

[hdamker]

@eric-murray @RandyLevensalor please check the changes as discussed

[tanjadegroot]

Comment on changelog.md update

[tanjadegroot]

@tanjadegroot All review comments should been addressed above. Please have a look and mark the conversations as resolved if this is the case.

Many thanks Herbert. looks great !
for some reason I do not have the RESOLVE button, so I marked with text :-(

/LGTM from Release Mgmt

[hdamker]

@tanjadegroot All review comments should been addressed above. Please have a look and mark the conversations as resolved if this is the case.

Sorry, I haven't thought about the fact that you need to be either the author of the PR or have write access to be able to resolve conversations. So it would have been on me to resolve. Thanks for adding your final comments.

[hdamker]

@tanjadegroot have corrected two of the other points which you have raised in camaraproject/Template_API_Repository#15 in 6c818e9