From 3c17992c850e56722c6869840569f7dee44d49c7 Mon Sep 17 00:00:00 2001 From: PEDRO DIEZ GARCIA Date: Mon, 15 Jul 2024 20:38:30 +0200 Subject: [PATCH] Carrier Billing APIs Readiness Checklist MetaRelase Fall24 --- ... Billing Refund-API-Readiness-Checkkist.md | 27 +++++++++++++ ...Carrier Billing-API-Readiness-Checklist.md | 40 +++++++++++++------ 2 files changed, 54 insertions(+), 13 deletions(-) create mode 100644 documentation/API_documentation/Carrier Billing Refund-API-Readiness-Checkkist.md diff --git a/documentation/API_documentation/Carrier Billing Refund-API-Readiness-Checkkist.md b/documentation/API_documentation/Carrier Billing Refund-API-Readiness-Checkkist.md new file mode 100644 index 0000000..d97f38b --- /dev/null +++ b/documentation/API_documentation/Carrier Billing Refund-API-Readiness-Checkkist.md @@ -0,0 +1,27 @@ +# API Readiness Checklist + +Checklist for Carrier Billing Refund v0.1.0 in r0.3. + +| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Comments | +|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:| +| 1 | API definition | M | M | M | M | Y | link | +| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | | +| 3 | Guidelines from ICM applied | O | M | M | M | Y | | +| 4 | API versioning convention applied | M | M | M | M | Y | | +| 5 | API documentation | M | M | M | M | Y | link | +| 6 | User stories | O | O | O | M | Y | link | +| 7 | Basic API test cases & documentation | O | M | M | M | Y | link | +| 8 | Enhanced API test cases & documentation | O | O | O | M | N | link | +| 9 | Test result statement | O | O | O | M | N | link | +| 10 | API release numbering convention applied | M | M | M | M | Y | | +| 11 | Change log updated | M | M | M | M | Y | link | +| 12 | Previous public release was certified | O | O | O | M | N | | + +To fill the checklist: +- in the line above the table, replace the api-name, api-version and the rx.y by their actual values for the current API version and release. +- in the Status column, put "Y" (yes) if the release asset is available or fulfilled in the current release, a "N" (no) or a "tbd". Example use of "tbd" is in case an alpha or release-candidate API version does not yet provide all mandatory assets for the release. +- in the Comments column, provide the link to the asset once available, and any other relevant comments. + +Note: the checklists of a public API version and of its preceding release-candidate API version can be the same. + +The documentation for the content of the checklist is here: [API Readiness Checklist](https://wiki.camaraproject.org/x/HQBFAQ) diff --git a/documentation/API_documentation/Carrier Billing-API-Readiness-Checklist.md b/documentation/API_documentation/Carrier Billing-API-Readiness-Checklist.md index b6a5745..6a92496 100644 --- a/documentation/API_documentation/Carrier Billing-API-Readiness-Checklist.md +++ b/documentation/API_documentation/Carrier Billing-API-Readiness-Checklist.md @@ -1,13 +1,27 @@ -# Carrier Billing API Readiness minimum criteria checklist - -
- -| No | Deliverables/Criteria | Mandatory | Status (Contributed/Approved/Pending/Validated/Partly-Validated)| -|----|-----------------------------------|-----------|------------------------| -| 1 |API Spec | Y | Contributed | -| 2 |API Implementation | Y | Contributed | -| 3 |API Documentation | Y | Contributed | -| 4 |User Stories | Y | Contributed | -| 5 |API test cases | Y | Not Contributed | -| 6 |Validated by at least 2 operators | Y | N/A | -| 7 |Security review | N | Contributed | +# API Readiness Checklist + +Checklist for Carrier Billing v0.3.0 in r0.3. + +| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Comments | +|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:| +| 1 | API definition | M | M | M | M | Y | link | +| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | | +| 3 | Guidelines from ICM applied | O | M | M | M | Y | | +| 4 | API versioning convention applied | M | M | M | M | Y | | +| 5 | API documentation | M | M | M | M | Y | link | +| 6 | User stories | O | O | O | M | Y | link | +| 7 | Basic API test cases & documentation | O | M | M | M | Y | link | +| 8 | Enhanced API test cases & documentation | O | O | O | M | N | link | +| 9 | Test result statement | O | O | O | M | N | link | +| 10 | API release numbering convention applied | M | M | M | M | Y | | +| 11 | Change log updated | M | M | M | M | Y | link | +| 12 | Previous public release was certified | O | O | O | M | N | | + +To fill the checklist: +- in the line above the table, replace the api-name, api-version and the rx.y by their actual values for the current API version and release. +- in the Status column, put "Y" (yes) if the release asset is available or fulfilled in the current release, a "N" (no) or a "tbd". Example use of "tbd" is in case an alpha or release-candidate API version does not yet provide all mandatory assets for the release. +- in the Comments column, provide the link to the asset once available, and any other relevant comments. + +Note: the checklists of a public API version and of its preceding release-candidate API version can be the same. + +The documentation for the content of the checklist is here: [API Readiness Checklist](https://wiki.camaraproject.org/x/HQBFAQ)