Use by RM admins only: Content for API release tracker template (v9 - 01/07/2025)

Use by RM admins only: Content for API release tracker template (v9 - 01/07/2025)

DO NOY COPY THE BLUE TEXT.

The below text is the content for the Confluence template for the API release tracker pages (to be used only by Confluence Admin to copy to the template page).

The template title should be :

<api-name> v<x.y.z>

The template page content: please copy all text below the line to the Confluence template page as the template content


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

Fall25 | N/A

choose one: N/A if the API is not (yet) planned to be part of a meta-release.

API name

<api-name>

the API name in lower-kebab-case

Target version

<x.y.z>

major.minor.patch version targeted for the next public release. Do NOT update with patch version (same version as used in the API Release Tracker page title)

Repository

<short link>

short link to API repository (edit link to keep repo name only)

Group

<short link>

short link to Sandbox/Sub-Project Confluence wiki home page (edit link to keep name only)

Maturity

initial | stable

choose one

Scope

<issue link>

short link to API scope GitHub issue (edit link to keep #number only)

API version

<OAS version field>

info.version field of the OAS file in the last (pre-)release (e.g. 0.2.0-alpha.1, 0.10.0-rc.2, 0.3.1, 1.0.0-rc.1, etc). Update with patch release.

M3 date

yyyy-mm-dd

update mandatory with final M3 pre-release date

Pre-release

<short tag link>

short link to the release. Update with each alpha and rc pre-release tag (edit link to keep rx.y only)

M4 date

yyyy-mm-dd

update mandatory with M4 public release date

Public release

<short tag link>

short link to the release. Update with M4 public release tag or patch release tag (edit link to keep rx.y only)

Patch date

 

update with each patch release date, if applicable

RM reviews

<short issue link>

RM review issue short link(s). Updated by Release Management only. Add for M3 and M4 (edit link to keep #number only)

Comments

free text

 

New

yes | no

choose one. Use yes if it is the first time the API is part of a meta-release, else use no.

Contacts

@name1, @name2

use @name format

 

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.