Page History

...

Planning and progress reporting on a meta-release

The planning and status of the ongoing meta-release is discussed in the Release Management working group meetings.

The meta-release planning and status is visible on the meta-release plan created for each meta-release. The meta-release progress data is obtained as follows:

• the Commonalities and ICM data is updated directly on the meta-release plan by the respective teams.
• the API data is managed by the API Sub Project teams on their API release trackers and pulled into the meta-release plan automatically.

The following actions are requested from the various teams to plan and provide visibility on the progress of a meta-release. They are also listed in the milestone table.

...

During the meta-release cycle, the Release Management team actions for progressing the meta-release are the following:

• Before Prepare meta-release page: before M0, the Release Management team shall create the meta-release plan (page) under under CAMARA meta-releases as follows:
  • Copy the following page Meta-release <meta-release name>, changing the parent paged to: CAMARA meta-releases (tick the "copy files and images" box).
  • Follow the instructions in red on the copied page.
• Request the TSC to declare the meta-release kick-off.

• M0
  • announce Announce the meta-release kick-off on the CAMARA mailing list (all@lists.camaraproject.org). This announcement indicates:
    
    • the Commonalities and ICM teams to prepare for M1 the scope definition of what they plan to put in the meta-release
    • all API Sub Projects release contacts to create the API release tracker for their next planned API version(s) as described here:   API release tracking process.
    • the Outreach Committee to start preparation of marketing activities based on information in the meta-release plan
  M1
  • Once available, check the final alpha releases PR of Commonalities & ICM and their release asset availability. If OK, submit to TSC for approval.
  • After TSC approval, announce M1 on release management and maintainers mailing lists.
• M1M2
  • check Check for Commonalities and ICM that all release assets are available in their final release-candidate PRs. 
  • If OK, request TSC to approve creation of the final release-candidate of Commonalities and ICM. Check that  
  • After TSC approval, and update of the meta-release plan is updated with the final release-candidate information tags of Commonalities and ICM. Announce , announce M2 milestone once the meta-release page is updated with the Commonalities and ICM release-candidate tags.
• M2
  
  • From M1, for
  M3
  • For all APIs, once available, check the first API release-candidate PR and, if OK, approve PR. 
  • Announce M3 milestone once all approved API release-candidates have update their API release tracker.
• M3M4
  • for For all APIs, once available, check readiness of final API release-candidate API PRs. Approval PR and, if OK, approve PR. Approval can start as soon as an API Sub Project indicates "M4: ready for RM" on the API release tracker in the comments field. It is not necessary to wait for the actual M4 date if an API release is ready before. Once
  • For all APIs, once available, check final API public-release -candidate PR, and, if OK, approve PR. for all API public-release PRs, check if OK and ask for formal TSC approval. 
  • Announce M4 milestone when all API public-releases are approved by TSC.
• M4M5
  
  • check Check that all API release trackers are updated with their public-release tag for the meta-release.
  • Propose meta-release content to TSC.
  • After TSC approval, publish the meta-release.
  • Announce the M5 meta-release on all@lists.camaraproject.org 
• M5
  • Review the release process with all teams and identify areas for improvement for
  M6
  • conduct a meta-release retrospective as input for the next meta release with all teams. A A meta-release feedback page is available to all to add comments, feedback and suggestions for improvement. Improvement proposals are submitted for I
  • Propose improvements for TSC approval to TSC and to be implemented for the next meat-release.
  • After TSC approval, announce M6 milestone
• M6

The actual milestone dates and status shall be updated on the meta-release plan when the milestone is achieved.

The status of the ongoing meta-release is discussed in the Release Management working group meetings.

Meta-release progress is visible on the meta-release plan created for each meta-release. The data is obtained as follows:

...

.

Commonalities and ICM

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

...