kyc-match v0.3.0
- Toshi Wakayama
- Tanja de Groot
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 | choose one |
API name | kyc-match | API name in lower-kebab-case |
Target version | 0.3.0 | major.minor.patch version. Do NOT update with patch version |
Repository | short link to API repository | |
Group | short link to Sandbox/Sub-Project Confluence wiki home page | |
Maturity | initial | choose one |
Scope | ย | short link to API scope GitHub issue |
API version | <OAS version field> | OAS definition version field of the last (pre-)release. Update with patch 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 | ย | update with each patch release date, if applicable |
RM reviews | <issue link> | RM review issue link(s). Add for M3 and M4. |
Comments | free text | ย |
New | no | choose one. Use yes if it is the first time the API is part of a meta-release, else use no. |
Contacts | @Toshi Wakayama @Fernando Prado Cabrillo | 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.