-
Notifications
You must be signed in to change notification settings - Fork 21
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
Public Release for Fall24 meta-release #139
Conversation
Set version to 1.0.0
Update Readiness Checklist
Update readme for r1.2
Update changelog for r1.2
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
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, one suggestion and one comment.
Please add @camaraproject/release-management_maintainers, as it is ready for review.
| 7 | Basic API test cases & documentation | O | M | M | M | Y | [PR #124](https://github.com/camaraproject/NumberVerification/pull/124/files) | | ||
| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | [PR #124](https://github.com/camaraproject/NumberVerification/pull/124/files) | |
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.
The status is either "tbd" with the PR, or you consider that PR 124 must be merged before the release PR, than you can already link here the coming .feature file.
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.
We have just merged the Test Definition.
I've updated the rc1.2 branch accordingly.
Add link for the test definition
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Test PR to update branch
Please review my ICM review on 1.1 |
The link in the last line of README.md is wrong. |
Fixed link to meeting minutes (last ine) Thanks @rartych
Change number_verification to number-verification
Change name from number_verification to number-verification
Took into account file name change: number_verification.yaml to number-verification.yaml
@@ -5,7 +5,7 @@ Feature: Camara Number Verification API device phone number share | |||
|
|||
# Input to be provided by the implementation to the tests | |||
# References to OAS spec schemas refer to schemas specified in | |||
# https://raw.githubusercontent.com/camaraproject/NumberVerification/main/code/API_definitions/number_verification.yaml | |||
# https://raw.githubusercontent.com/camaraproject/NumberVerification/main/code/API_definitions/number-verification.yaml |
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.
Is somewhere defined which version of the API definition the .feature file refers to? This link goes to main and therefore potentially into "wip".
Maybe a relative link would be better to stay within the tag/branch, but I don't think this is possibly for raw content. An alternative would be to link just to /code/API_definitions/number_verification.yaml
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.
I've applied your suggestion.
Changed reference path to the yaml.
Changed reference path to the yaml.
…e to number-verification-device-phone-number-share.feature + make linting happy
documentation/API_documentation/NumberVerification-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
…hecklist.md Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
In the path: section there is |
fixed X-Correlator to x-correlator.
Thanks to catch this one Rafal |
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.
- Update versions in test plans: Given the resource "/number-verification/v0 -> Given the resource "/number-verification/v1
documentation/API_documentation/NumberVerification-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
…hecklist.md Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
changed "/device-phone-number/v0" to "/device-phone-number/v1"
changed /number-verification/v0 to /number-verification/v1 in the background section
Thank @jlurien |
Let's wait to decision on camaraproject/ReleaseManagement#89 to merge this |
Added sentences in doc as mentioned in #116
Add a line to indicate that we updated the documentation part of the yaml
Following discussion in today WG meeting & sync with @hdamker I've updated the yaml to add a clarification before the sequence diagram. Changelog has been also updated. |
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Please see camaraproject/ReleaseManagement#89 on how to update the Test result statement in the API readiness checklist for this Fall24 meta-release. |
Taking care of the Test result statement accordingly to camaraproject/ReleaseManagement#89
Thanks @tanjadegroot |
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.
Release PR approved (on behalf of Release Management)
@bigludo7 PR ready to be merged and r1.2 can be created.Please update https://wiki.camaraproject.org/display/CAM/NumberVerification++API+Release+Tracking with date for M4 and link to r1.2 when it is created. Thanks
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
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Related to issue #107
Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
Missing link for Test Statement
PR for Test Definition no yet merged
Changelog input
Additional documentation
This section can be blank.