...
The release tracking for Commonalities and ICM is done directly on the meta-release plan of the active meta-release accessible here: CAMARA meta-releases (select the active meta-release form the list).
The following explains the fields of the Commonalities and ICM table on the meta-release plan:
...
- before M0:
- Starting from the M2 of the previous meta-release, prepare the scope definition for the upcoming meta-release.
- Start implementing the scope through one or more alpha releases.
- M0
- As soon as possible after M0, fix the scope definition for the release for the meta-release:
- Record scope in a dedicated GitHub issue, e.g. called "Fall24: Commonalities / ICM scope".
- Submit scope issue for TSC review
- Develop final Commonalities & ICM scope through one or more alpha releases
- Update data in the meta-release plan with each alpha release
- Create final alpha release PRs and submit to Release Management
- After TSC approval, create approved final alpha release for Commonalities & ICM
- Update the meta-release plan with the alpha release tag
- As soon as possible after M0, fix the scope definition for the release for the meta-release:
- M1
- Fix bugs raised by users through one or more release-candidates
- Update release tracker on meta-release page with each release-candidate
- Create final release-candidate PR and submit to Release Management for checking
- After TSC approval:
- Create the final release-candidate for Commonalities & ICM
- Update the meta-release page for Commonalities & ICM with release-candidate tag
- Announce M2 milestone. These Commonalities and ICM final release-candidates shall be used by the API Sub Projects to work with for their API release-candidate development.
- Start the scope definition and alpha releases for the next meta-release.
- M3 and M4
- During API development, changes to the final Commonalities or ICM release-candidates may be requested, leading to new release-candidates to be reflected on the meta-release page.
- The public-release PR of the Commonalities and ICM will only be created latest 2 weeks before the M4 date. Once committed, these will also be used for M5 for inclusion in the meta-release.
- Fix bugs raised by API testers through one or more release-candidates
- Create public-release PR for Commonalities & ICM
- After Release Management check and TSC approval of the public-release PR
- Create the public-release
- Update the meta-release page with public-release tag
- M5
- Provide feedback on meta-release
- M6
API Sub Projects
API release tracking
API Sub Project teams shall create and update the API release tracker for each of their API version(s) as follows:
- Create the API release tracker as described here: API release tracking process
- With each alpha or release-candidate API version, the API version and release tag shall be updated.
- The actual milestone dates shall be put in the release tracker when the milestone is passed.
- When M4 is successfully passed, the link to the public-release tag shall be added.
...
- If an API release is not visible, please check that the correct meta-release label is added to the API release tracker page.
Milestone activities
The following are the actions for milestones:
...