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).
...
----------------------------
API release trackers provided 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 a the meta-release or not.
If not planned as to be part of a the meta-release, remove the page label “camara-spring25”springxx/fallxx”, and add the label “camara-other”.
| Page Properties |
|---|
Meta-release | Spring25 | N/A (choose one) | API name | <api-name> | Target version | <major.minor.patch> | Repository | <short link to API repo> | Group | <short link to Sandbox/Sub-Project Confluence wiki home page> | Maturity | initial | stable | Scope | <short link to GitHub issue> | API version | <OAS definition version field of the last (pre-)release> | M3 date | yyyy-mm-dd (update only with final M3 pre-release date) | Pre-release | <short tag link> (update with each alpha and rc pre-release tag) | M4 date | yyyy-mm-dd (update with only with M4 public release date) | Public release | <short tag link> (update with M4 public release tag, or patch release tag) | Patch date | yyyy-mm-dd (update with each patch public release) | RM reviews | <RM review issue link(s)> | Comments | free text | Contacts | @ name1, @ name2 |
|
...