Fall25 - M3 Milestone - r1.1 - version v0.1.0 Release Candidate#14
Conversation
|
Hi @chinaunicomyangfan , I have just found that the yaml file has two 403 errors, Thanks, |
Kevsy
left a comment
There was a problem hiding this comment.
@chinaunicomyangfan thanks for the PR!
Please can you check my review comments/suggestions for:
- CHANGELOG.MD
- README.MD
- subscription-status-API- Readiness-Checklist
- subscription-status.feature
Please note you will also need to change the subscription-status.yaml:
XCorrelatorneeds to be a schema object , see camaraproject/Commonalities#480
Hi @chinaunicomyangfan , please can you provide the updates? I will not be able to complete the release management review until the fixes are made. Thanks! |
@Kevsy Thanks a lot for your suggestion, I totally approve. |
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
|
Thanks for the updates @chinaunicomyangfan ! One more change is required:
|
Add the mandatory Authorization and authentication text
yaml has been updated , please review |
| The below sections record the changes for each API version in each release as follows: | ||
|
|
||
| * for an alpha release, the delta with respect to the previous release | ||
| * for the first release-candidate, all changes since the last public release | ||
| * for subsequent release-candidate(s), only the delta to the previous release-candidate | ||
| * for a public release, the consolidated changes since the previous public release | ||
| The below sections record the changes for each API version in each release as follows: | ||
|
|
||
| * for an alpha release, the delta with respect to the previous release | ||
| * for the first release-candidate, all changes since the last public release | ||
| * for subsequent release-candidate(s), only the delta to the previous release-candidate | ||
| * for a public release, the consolidated changes since the previous public release |
There was a problem hiding this comment.
Duplication, please remove one instance
Delete duplication
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Thanks, @hdamker ,done, please review. |
|
@chinaunicomyangfan just one small change to make: Please can you add a |
Add description to the /retrive-subscription-status path
@Kevsy Description added, please review,thanks. |
| tags: | ||
| - Retrive Subscription Status | ||
| description: | | ||
| Oobtain the business subscription status of the provided phone number, including Voice/SMS inbound, Voice/SMS outbound, and data service status. |
There was a problem hiding this comment.
| Oobtain the business subscription status of the provided phone number, including Voice/SMS inbound, Voice/SMS outbound, and data service status. | |
| Obtain the business subscription status of the provided phone number, including Voice/SMS inbound, Voice/SMS outbound, and data service status. | |
There was a problem hiding this comment.
Thanks,done
There was a problem hiding this comment.
Thanks @chinaunicomyangfan - now approved on behalf of release management.
Next steps for the codeowners:
-
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)
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
This PR implements the scope
The PR updates all the file in terms of release number referring to r1.1 and version v0.1.0-rc.1
CHANGELOG.MD, README.MD & Readiness check list updated version are provide
Which issue(s) this PR fixes:
Fixes #12
Changelog input