Versions Compared

Old Version 57

changes.mady.by.user Tanja de Groot

Saved on

compared with

New Version 58

changes.mady.by.user Tanja de Groot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Commonalities and ICM teams shall respectively update and maintain their information on the meta-release page following the below steps.

Release tracking

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).

...

  • 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
  • M1
    • Fix bugs raised by users through one or more release-candidates
    • Update release tracker on data in the meta-release pageplan with each release-candidate
    • Create final release-candidate PR and submit to Release Management for checking
    • After TSC approval:Create the , create approved final release-candidate for Commonalities & ICM
    • Update the meta-release page for Commonalities & ICM with plan with the final  release-candidate release tagAnnounce M2 milestone. These Commonalities and ICM . The final release-candidates candidate shall be used by the API Sub Projects to work with for their API release-candidate development.
    • Start the scope definition and alpha releases release 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

Release tracking

API Sub Project teams shall create and update the API release tracker for each of their API version(s) as follows: 

...