• To be closed when the full process of MetaRelease v0.4 is covered (i.e. latest issue to be closed)
• Milestone achieved with it: M4

Administrative Procedures:

• Based on: https://github.com/camaraproject/ReleaseManagement/blob/main/documentation/API-Readiness-Checklist.md

1. Update API Readiness Checklist format and information: Update API Readiness Checklist format and information for Meta-Release Fall24 #163
2. Update User Stories: Update User Stories Document for Meta Release v0.4 - Fall24 #162
3. Have initial Testing Feature: Testing - Generate Gherkin Testing feature(s) for Carrier Billing for Meta-Release Fall24 #159
   

M3 Milestone:
Generate Release Candidate Carrier Billing versions for Meta Release v0.4 - Fall24 #164

Issue created to generate API Readiness Information according to Release management guidelines.
PR triggered: PR#166

To be adapted for M3 milestone status (pending). For M4 Milestone an update of API Readiness Checklist will be done.

Issue created to update User Stories information according to MetaRelease Fall24 scope
PR is still pending. Target: 09th August

Expected to be managed within M4 Milestone.

Issue updated to reflect that as current Release management Guidelines, Basic testing would be enough
PR is still pending. Expected to have during August. Target: Middle 12th August week.


Expected to be managed within M4 Milestone.

Issue to track the management of generated the release candidate proposals for Carrier Billing Payment and Carrier Billing Refunds
PR triggered: PR#167

Approved by WG. Waiting Approval by RM maintainers WG.

Minor updates done regarding:

• Adapt recent updates in "# Authorization and authentication" section from I&CM - Replace link into main branch of Identity and Consent Management within "Authorization and authentication" text template IdentityAndConsentManagement#186
• Remove "termsOfService" and "contact" from OAS info object

Josef Poneš comments about changes or enhancements for CB APIs.

Rafal and Pedro indicates enhancements and changes can be discussed as this is continuous specification track. Currently focused in MetaRelease process. For reaching formal public v1.0 specs, that will take more time because it is needed to have "live" implementations tested by at least 2 Telco Operators and not only depends on Specification work done within the WG.