-
Notifications
You must be signed in to change notification settings - Fork 9
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
Release r2.1 (Release Candidate) #202
Conversation
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.
Thanks a lot @PedroDiez !
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
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.
Impressive work, very few comments from Release Management perspective!
Please have a view on the inconsistent statements regarding the condition for the error response 422 UNNECESSARY_IDENTIFIER.
documentation/API_documentation/carrier-billing-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
documentation/API_documentation/carrier-billing-refund-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
…Checklist.md Co-authored-by: Herbert Damker <[email protected]>
…diness-Checklist.md Co-authored-by: Herbert Damker <[email protected]>
Co-authored-by: Herbert Damker <[email protected]>
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.
Thanks @PedroDiez for the fixes. Looks good now from Release Management perspective.
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.
Thanks a lot @PedroDiez for the great work !
Don't forget to update your release trackers after creating the pre-release 😄 |
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Generation of release r2.1 (release candidate) for Carrier Billing APIs Family
This release contains the definition and documentation of
The API definition(s) are based on
Which issue(s) this PR fixes:
Fixes #196
Fixes #197
Fixes #199
Fixes #200
Special notes for reviewers:
Alignments with Commonalities r2.2 in advance in commit 0dddf48
Changelog input
Additional documentation
This section can be blank.