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 your API release tracker page by clicking on the label icon at the top or bottom of the page and adding "camara-<meta-release name>", e.g. “camara-spring25”.
Remove these lines in red.
Test of different layout in table below:
, remove the page label “camara-springxx/fallxx”, and add the label “camara-other”.
...
Repository
...
Page Properties | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Meta-release
...
Spring25
...
API name
...
<api-name>
...
Target version
...
<major.minor.patch>
|
...
Group
...
<short link to Sandbox/Sub-Project Confluence wiki home page>
...
Maturity
...
initial | stable
...
Scope
...
<short link to GitHub issue>
...
Readiness checklist
...
<link to <api-name>-API-Readiness-Checklist.md>
...
API version
...
<OAS definition version field of the last (pre-)release>
...
M3 release
...
PR# or <short tag link>
...
M3 date
...
yyyy-mm-dd
...
M4 release
...
PR# or <short tag link>
...
M4 date
...
yyyy-mm-dd
...
Patch
...
PR# or <short tag link>
...
Patch date
...
yyyy-mm-dd
...
RM reviews
...
Mx: <RM review issue link>
|
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.