Release r1.2 (Fall'25 M4)#18
Conversation
|
Hi @chinaunicomyangfan , In the yaml file, ErrorInfo properties description needs to be fixed to align with the latest Commonalities, I think. L.197 description of ‘code’ and L.200 description of ‘message’. I don't have enough time now, so, please look at other APIs' Commonalities alignment PRs. Thanks, |
You can use https://github.com/camaraproject/QualityOnDemand/pull/484/files, code/API_definitions/qos-profiles.yaml as an example. And keep the order ( |
Updates descriptions in ErrorModel
|
Thanks, @ToshiWakayama-KDDI and @hdamker .I have updated the descriptions in ErrorMode in 4bfcd3c , please review. |
hdamker
left a comment
There was a problem hiding this comment.
@chinaunicomyangfan this is not the full review by release management, I have just seen the two issues which you have introduced with the last two commits and suggest to fix them.
Thanks, GitHub links are looking good now again.
bigludo7
left a comment
There was a problem hiding this comment.
Hello
Look good now and thanks @hdamker for the catch following latest update.
We can move forward.
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)
|
Checked and everything is fine |
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Publication of Fall'25 M4 public release of subscription-status v0.1.0