Add the meta-release label to the page by clicking on the label icon at the top of the page and adding "camara-<meta-release name>", e.g. camara-fall24, camara-spring25, etc.
Remove these lines in red.
API release checklist
Nr | API release assets | alpha | release-candidate | public-release | |
initial | stable | ||||
1 | API definition |
|
|
|
|
2 | Application of design guidelines from Commonalities | N |
|
|
|
3 | Application of profile guidelines from ICM | N |
|
|
|
| 4 | API versioning conventions followed |
|
|
|
|
| 5 | API release numbering conventions followed |
|
|
|
|
6 | Linting rules enabled |
|
|
|
|
7 | Protected branches enabled |
|
|
|
|
8 | API documentation |
|
|
|
|
9 | Maintainers doc (from at least 3 distinct companies) |
|
|
|
|
10 | Codeowners doc (from at least 3 distinct companies) |
|
|
|
|
11 | Release notes according to template |
|
|
|
|
12 | User stories |
|
|
|
|
13a | Sunny day API test cases and documentation | N |
|
|
|
13b | Full set of API test cases and documentation | N | N |
|
|
| 14 | Test results (API test cases passed) | N | Y |
|
|
15 | Release-candidate API version tested in at least 2 operator implementations | N | N |
|
|
16 | initial public-release API version certified and launched in at least 2 operators is needed to become stable | N | N | N |
|
To be part of a meta-release, minimally the initial release assets need to be provided.
Additional Information
Add any other useful information about the status of the release here.