Use by RM admins only: Content for API release tracker template (v7 - 08/10/2024)
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).
ย ---- Start of template (please copy the below from upper red lines up to and including the last line of this page to the Confluenceย template) ----
----------------------------
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 or not.
If not planned to be part of the meta-release, remove the page label โcamara-springxx/fallxxโ, and add the label โcamara-otherโ.
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 mandatory 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 mandatory with M4 public release date) |
Public release | <short tag link> (update with M4 public release tag or patch release tag) |
Patch date | ย |
RM reviews | <RM review issue 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 API version here.
ย