...
- In the page title, change <meta-release name> to the actual meta-release name (e.g. Fall25, Spring26, etc).
- At the top of the page, click the label icon and create the new meta-release label: "camara-<meta-release name>" e.g. camara-fall25, camara-spring26, etc.
- Remove the non-applicable timeline
- Remove the non-applicable milestone dates table
- if the dates need to be adjusted, the source PPT of the meta-release schedule is attached to this page: RM templates to copy
- picture display size = 960px and middle size.
- In the "API release contacts" section, update the macro by adding the newly created meta-release label in the "Labels" section
- In the "API version status" section, update the macro by adding the newly created meta-release label in the "Labels" section
- Then remove these red lines.
| Table of Contents |
|---|
Timeline
Milestone dates
| Milestone | Target date | Status | Actual date | Comment |
|---|---|---|---|---|
| M0 | 09-30 | kick-off preparation |
|
|
| M1 (Commonalities & ICM) | 10-15 | |||
| M2 (Commonalities & ICM) | 12-07 | |||
| M3 (API Sub Projects) | 12-21 | |||
| M4 (API Sub Projects) | 02-28 | |||
| M5 | 03-15 | |||
| M6 | 03-31 |
...
| Working Group | Commonalities | ICM |
|---|---|---|
Target version | 1.0.0 | |
Target scope | <shortened issue link> | <shortened issue link> |
M1 date | yyyy-mm-dd | yyyy-mm-dd |
M2 date | yyyy-mm-dd | yyyy-mm-dd |
(Pre)release tag | <shortened release tag link> | <shortened release tag link> |
M5 date | yyyy-mm-dd | yyyy-mm-dd |
| Public-release tag | <shortened release tag link> | <shortened release tag link> |
API release contacts
...
API version release status
...
| Page Properties Report | ||||||||
|---|---|---|---|---|---|---|---|---|
|
API release contacts
Page Properties Report firstcolumn API headings Contacts sortBy title cql label = "camara-fall24" and space = currentSpace()