API Version for M4 #154
API Version for M4 #154
Conversation
release number update to v0.3.0: camaraproject#153
FabrizioMoggio
requested review from
bigludo7 and
chinaunicomyangfan
as code owners
|
@FabrizioMoggio As CallForwardingSignal was promoted to the "Incubating" stage, please do the following changes (either here in the release PR or as a separate issue and PR:
|
There was a problem hiding this comment.
Sorry, the PR on the template is still waiting for review and merge, but ProjectStructureAndRoles.md is already updated:
camaraproject#156 Co-authored-by: Herbert Damker <[email protected]>
camaraproject#156 Co-authored-by: Herbert Damker <[email protected]>
camaraproject#156 Co-authored-by: Herbert Damker <[email protected]>
|
@hdamker I don't get why Merging is blocked. In my understanding I have included in the PR all the requested changes, Isn't it? |
There was a problem hiding this comment.
I'm not an expert for the test definition files, but it seems that the "CAMARA Common Artifact C02 - Test scenarios for phoneNumber errors" are not applied (maybe because also the error responses are not aligned?).
There was a problem hiding this comment.
We have implemented some test scenarios on phone number but not those one. Is it mandatory to be compliant with that for an Incubated API or can we align the API after Spring25?
documentation/API_documentation/call-forwarding-signal-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
ICM - Authorization and authentication: camaraproject#158 Alignment with Commonalities: camaraproject#159 Error 404: camaraproject#160
camaraproject#157 Co-authored-by: Herbert Damker <[email protected]>
camaraproject#162 Co-authored-by: Herbert Damker <[email protected]>
release number update to v0.3.0
What type of PR is this?
What this PR does / why we need it:
This PR updates the release version to 0.3.0. Stable release for M4.
Which issue(s) this PR fixes:
#153