-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Version for M4 #154
API Version for M4 #154
Conversation
release number update to v0.3.0: camaraproject#153
@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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 <herbert.damker@telekom.de>
camaraproject#156 Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
camaraproject#156 Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
@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? |
code/Test_definitions/call-forwarding-signal-unconditional.feature
Outdated
Show resolved
Hide resolved
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 <herbert.damker@telekom.de>
camaraproject#162 Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
documentation/API_documentation/call-forwarding-signal-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
…diness-Checklist.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that is strange, I don't have that void raw in my file. Anyway good catch, thank you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All my review comments are addressed, so LGTM from release management perspective. As there were a few larger changes, I propose that @bigludo7 and @chinaunicomyangfan are doing a thorough review before the PR is merged (can be done next week).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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