Skip to content

Release Candidate r3.1#232

Merged
PedroDiez merged 12 commits intocamaraproject:mainfrom
PedroDiez:r3.1
Jul 18, 2025
Merged

Release Candidate r3.1#232
PedroDiez merged 12 commits intocamaraproject:mainfrom
PedroDiez:r3.1

Conversation

@PedroDiez
Copy link
Copy Markdown
Collaborator

@PedroDiez PedroDiez commented Jun 25, 2025

What type of PR is this?

  • documentation
  • subproject management

What this PR does / why we need it:

Release 3.1 (Release candidate) PR for Carrier Billing APIs within Fall25 MetaRelease (M3)

Which issue(s) this PR fixes:

Carrier Billing:
Fixes #214
Fixes #216
Fixes #223
Fixes #224
Fixes #225

Carrier Billing Refund:
Fixes #216
Fixes #219
Fixes #220
Fixes #221

Special notes for reviewers:

Carrier Billing:
Fixes #214. Already covered in PR #217
Fixes #216. Already covered in PR #226
Fixes #223. Already covered in PR #229
Fixes #224. Covered in this PR
Fixes #225. Already covered in PR #230

Carrier Billing Refund:
Fixes #216. Already covered in PR #226
Fixes #219. Already covered in PR #229
Fixes #220. Covered in this PR
Fixes #221. Already covered in PR #230

Changelog input

 Release Candidate r3.1 for Carrier Billing APIs

Additional documentation

N/A

bigludo7
bigludo7 previously approved these changes Jun 29, 2025
Copy link
Copy Markdown
Collaborator

@bigludo7 bigludo7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Thanks @PedroDiez

@PedroDiez PedroDiez marked this pull request as ready for review June 30, 2025 16:14
@PedroDiez PedroDiez requested a review from bigludo7 June 30, 2025 16:17
@PedroDiez
Copy link
Copy Markdown
Collaborator Author

LGTM Thanks @PedroDiez

Thanks for initial review @bigludo7

bigludo7
bigludo7 previously approved these changes Jul 1, 2025
Copy link
Copy Markdown
Collaborator

@bigludo7 bigludo7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Contributor

@jlurien jlurien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is some misalignment with the API names:
In the info.title it says "Carrier Billing Refunds", but it the Confluence and in al other places it is singular: "Carrier Billing Refund", we may need to adjust the title then.
For Carrier Billing, in Confluence and trackers it is called "Carrier Billing Checkout", but the term Checkout does not appear in the spec. Should we rename it in Confluence officially to just "Carrier Billing"

@jlurien jlurien requested a review from a team July 9, 2025 12:02
@PedroDiez
Copy link
Copy Markdown
Collaborator Author

There is some misalignment with the API names: In the info.title it says "Carrier Billing Refunds", but it the Confluence and in al other places it is singular: "Carrier Billing Refund", we may need to adjust the title then. For Carrier Billing, in Confluence and trackers it is called "Carrier Billing Checkout", but the term Checkout does not appear in the spec. Should we rename it in Confluence officially to just "Carrier Billing"

Think makes sense, cc @bigludo7, @rartych

I am aligning that way:
Carrier Billing Refunds -> info.title: Carrier Billing Refund
Carrier Billing -> Update release trackers

Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
PedroDiez and others added 5 commits July 10, 2025 14:06
Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
…Checklist.md

Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
…diness-Checklist.md

Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
bigludo7
bigludo7 previously approved these changes Jul 10, 2025
@bigludo7
Copy link
Copy Markdown
Collaborator

There is some misalignment with the API names: In the info.title it says "Carrier Billing Refunds", but it the Confluence and in al other places it is singular: "Carrier Billing Refund", we may need to adjust the title then. For Carrier Billing, in Confluence and trackers it is called "Carrier Billing Checkout", but the term Checkout does not appear in the spec. Should we rename it in Confluence officially to just "Carrier Billing"

Think makes sense, cc @bigludo7, @rartych

I am aligning that way: Carrier Billing Refunds -> info.title: Carrier Billing Refund Carrier Billing -> Update release trackers

Yes make sense.
+1 for using singular for refund and for removing checkout term.

@PedroDiez PedroDiez requested a review from jlurien July 10, 2025 12:23
@PedroDiez PedroDiez requested a review from bigludo7 July 10, 2025 12:33
bigludo7
bigludo7 previously approved these changes Jul 10, 2025
Copy link
Copy Markdown
Collaborator

@bigludo7 bigludo7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Pedro (and to Jose for the review)

Copy link
Copy Markdown
Contributor

@jlurien jlurien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of comments, for your consideration

README.md Outdated
<br>This is a release candidate. Until the public release there are bug fixes to be expected. The release candidate is suitable for implementors, but it is not recommended to use the API with customers in productive environments.

* The pre-release **r3.1 - rc** is available in [r3.1](https://github.com/camaraproject/CarrierBillingCheckOut/tree/r3.1), and includes the following APIs:
- API name: Carrier Billing (Payment) - API Definition v0.5.0-rc.1 with inline documentation:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the "(Payment)" is not part of the official API name I would remove it from here

Copy link
Copy Markdown
Collaborator Author

@PedroDiez PedroDiez Jul 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes makes fully sense, thanks for the catch Jose

I make update

@bigludo7
Copy link
Copy Markdown
Collaborator

Note: I have approved as codeowner and not on behalf release management reviewers.
For the release management it is up to @jlurien to approve.

Copy link
Copy Markdown
Contributor

@jlurien jlurien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved on behalf of @camaraproject/release-management_reviewers

Next actions to fulfill M3:

  • 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)

@PedroDiez PedroDiez merged commit 996400f into camaraproject:main Jul 18, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

3 participants