This is the baseline for the Confluence template for API release tracker pages (to be used only by Confluence Admin to copy to the template page).
...
----------------------------
If API release trackers provide visibility on the development of an API version to the wider CAMARA community and beyond. A tracker can be created for any API version, whether planned for the meta-release , add or not.
If not planned to be part of the meta-release label to , remove 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.
label “camara-springxx/fallxx”, and add the label “camara-other”.
| Page Properties |
|---|
Fall24 A A (choose one) | API name | <api-name> |
Group | <API group name>Target version | <major.minor.patch> | Repository | <short link to |
Sub Project initial| Target version | <major.minor.patch> | Maturity level | Group | <short link to Sandbox/Sub-Project Confluence wiki home page> | Maturity | initial | stable | Scope | <short link to GitHub issue> |
Readiness checklist | | Github file macro |
|---|
| collapsible | true |
|---|
url | https://github.com/camaraproject/QualityOnDemand/blob/r1.2/documentation/API_documentation/quality-on-demand-API-Readiness-Checklist.md version field>definition version field of the last (pre-)release> | M3 date | yyyy-mm-dd |
M3 (update mandatory with final M3 pre-release date) | Pre-release |
PR# or <short tag link> (update with each alpha and rc pre-release tag) | M4 date | yyyy-mm-dd |
M4 (update mandatory with M4 public release date) | Public release |
PR# or <short tag link> (update with M4 public release tag or patch release tag) | Patch date | | RM |
reviewMx: link>link(s)> | Comments | free text | Contacts | @ name1, @ name2 |
|
For guidelines on how to fill the table, see here: API release trackers
Additional Information
Add any other useful information about the status of the release API version here.