Release r1.2 (M4 Fall25)

[Masa8106]

What type of PR is this?

• subproject management

What this PR does / why we need it:

• Set API versions
  • qos-booking v0.1.0
  • qos-booking-and-assignment v0.1.0
• Update test definitions
• Update changelog
• Update readme
• Update readiness checklist files

Which issue(s) this PR fixes:

Fixes #46

Special notes for reviewers:

[hdamker]

Looks good ... few suggestions below

Note: I haven't done the official release review, just pre-reviewed as member of QualityOnDemand

[Masa8106]

@hdamker, two new PRs (PR #54 and PR #55 ) were created after creating this release PR. The PRs propose just to fix bugs. So let me confirm whether we can merge the two PRs into main as r1.2 release. If possible, I would like to do that.

[hdamker]

@hdamker, two new PRs (PR #54 and PR #55 ) were created after creating this release PR. The PRs propose just to fix bugs. So let me confirm whether we can merge the two PRs into main as r1.2 release. If possible, I would like to do that.

Yes, that is my expectation: to take these fixes into r1.2.

[jlurien]

LGTM, please sync with latest commits in master

[hdamker]

LGTM, please sync with latest commits in master

+1 ... the two open PRs look ready to be merged into main, and then update the release PR from main.

[Masa8106]

The two PRs have been merged. And this release PR has been updated.
So I think this PR is ready to bereviewed by release manegement. I will wait for an approval by it.

[Masa8106]

@jlurien, for my clarification, have you approved this PR as Release Managemetn team, not as code owner? If yes, I will merge this PR.

[Masa8106]

@Kevsy , Thank you for your comments. I have updated based on your comments. Please review it again.

[Kevsy]

Approved on behalf of Release Management 👏

Next steps for the team:

• PR merged (by API repository codeowner)
• Release created within GitHub (by API repository codeowner)
• Release Tracker updated (with creation date of the release and the release tag link)

[Masa8106]

@Kevsy , thank you so much for reviewing it.
@jlurien , may I ask you to review it again? Another code owner review is required for merge.

[hdamker]

@jlurien , may I ask you to review it again? Another code owner review is required for merge.

@Masa8106 Jose is on vacation and will not be back on time if I understood it right. I have reviewed the changes since his review and haven't found anything critical. The changes in .feature files aligned them with what we have in QualityOnDemand. Given that I can offer to bypass the rules as admin and merge the PR for you. Just let me know if that is ok for you.

[Masa8106]

@hdamker Thank you for letting me know that. I will be happy if we can bypass the rule, in order to release this in time.

[hdamker]

LGTM and will merge it now.

[Kevsy]

HI @Masa8106 , you can now proceed with the final tasks:

• Release created within GitHub (by API repository codeowner)
• Release Tracker updated (with creation date of the release and the release tag link)

[Masa8106]

Hi @Kevsy , thank you for reminding me the final tasks. I have done them.