Skip to content
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

Carrier Billing Scope for Meta Release v0.4 - Fall24 #155

Closed
PedroDiez opened this issue May 7, 2024 · 5 comments
Closed

Carrier Billing Scope for Meta Release v0.4 - Fall24 #155

PedroDiez opened this issue May 7, 2024 · 5 comments
Labels
subproject management Actions related to repository/releases

Comments

@PedroDiez
Copy link
Collaborator

Problem description
Meta-Release v0.4 - https://wiki.camaraproject.org/display/CAM/Meta-release+Fall24 provides a roadmap about the different WGs.
En each of them a set of features need to be discussed in order to agree within the scope of this meta-release

Commonalities example camaraproject/Commonalities#175

Therefore in Carrier Billing SubProject we need to agree in the scope for this WG within the context of that Meta Release

Expected action
Have closed scope for Carrier Billing with the MetaRelease

Additional context
N/A so far

@PedroDiez PedroDiez added the subproject management Actions related to repository/releases label May 7, 2024
@PedroDiez
Copy link
Collaborator Author

Please comment every participant interested in the workign group

@PedroDiez
Copy link
Collaborator Author

Telefonica input:

  • Having Carrier Billing v0.3.0
  • Having Carrier Billing Refund (final decision in which API is something that can be discussed later)

In terms of specific points:

@PedroDiez
Copy link
Collaborator Author

PedroDiez commented Jul 10, 2024

@PedroDiez
Copy link
Collaborator Author

PedroDiez commented Sep 5, 2024

Closed as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subproject management Actions related to repository/releases
Projects
None yet
Development

No branches or pull requests

1 participant