Versions Compared

Old Version 25

changes.mady.by.user Tanja de Groot

Saved on

compared with

New Version Current

changes.mady.by.user Tanja de Groot

Saved on

Key

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

Table of Contents

Introduction

A CAMARA meta-release is the way CAMARA brings its APIs to market.

A meta-release consists of a set of public versions of curated APIs that went though the CAMARA meta-release process.

WIP

...

The purpose of this document is to describe the cadence, processes, milestones, and associated tasks used in the CAMARA release cycle. See CAMARA meta-releases for information and schedule for specific releases.

Process

CAMARA meta-releases are scheduled twice per year at approximately 6 month intervals (March and September). Meta-releases are named after major world cities in alphabetical order.

...

define

  • the milestones of the meta-release (this page), and the supporting Meta-release Process documentation
  • the activities expected from the different teams to move from one milestone to the next
  • the way to report progress on the meta-release itself, on the Commonalities and ICM releases and on API releases

For the schedule and content of actual planned meta-releases, see CAMARA meta-releases.

Meta-release milestones

Meta-release milestones and their associated actions are used to progress and track the status of the meta-release. 

  • A meta-release has 6 milestones, M0 through M6 described below. 
  • For the typical milestone dates

...

  • of a meta-release, please see

...

Meta-releases are administered and tracked by

  • the CAMARA Release Managers, supported by
  • the release contacts of the Commonalities and ICM working groups 
  • the release contacts of the API Sub-projects

The teams can put their release contact names on the Sub-project Release Contacts (Maintainers) page.

The ongoing meta-release status is discussed in the Release Management working group meetings and recorded on the meta-release page.

Release Milestones

Release milestones and their associated tasks, are used to track the status of the meta-release. The milestones and management tasks used in the release process are described in the table below.

...

Timeline

update

...

Week nr

...

  • Scope of Work Products clarified.
  • Identify commonalities work products.
  • Create initial PRs for commonalities.
  • Agree on the scope of commonalities.
  • TSC Approval.

...

The following table lists the meta-release milestones, and includes a high level view of the activities expected from the various teams to reach these milestones. 

More details on these for each team are documented here: 


Milestone / start date

Actors & Activities for next milestone

Timeline

Week Nr

pre-M0 activities
  • Release Management: prepare meta-release plan
  • Commonalities & ICM: define scope and start alpha release development
  • TSC: declare M0 - meta-release kickoff


M0 

Meta-release kickoff

M00
activities for M1 start @ M0
  • Commonalities & ICM: fix scope and develop final alpha release for M1
  • API Sub Groups: check Commonalities and ICM scope definition to assess API impact
  • TSC: approve Commonalities and ICM scope and final alpha release
  • Release Management: Declare M1 - Commonalities and ICM alpha release available
2 weeks

M1

Alpha Commonalities & ICMM0 + 2 weeks2
activities for M2 start @ M1
  • API Sub Groups: align to Commonalities and ICM alpha release and provide feedback
  • Commonalities & ICM: Fix bugs and prepare final release-candidate for M2
  • TSC: approve Commonalities and ICM final release-candidate
  • Release Management; declare M2 - Commonalities and ICM release-candidate available
7 weeks

M2

Release-candidate Commonalities & ICMM1 + 7 weeks9
activities for M3 start @ M1
  • API Sub Projects: prepare API scope and develop alpha releases, ending by the first release-candidate for M3
  • TSC: review scope of APIs (case by case selection)
  • Release Management: check API readiness of each API and declare M3 - all API first release-candidates available
9 weeks

M3

Release-candidate APIs (Code Freeze)

M1 + 9 weeks

9
activities for M4 start @ M3
  • API Sub Projects: fix bugs and prepare public-release
  • Commonalities & ICM: prepare public-release
  • Release Management: check API readiness of each API and declare M4 - all API public-releases available
  • TSC: give formal approval of Commonalities, ICM and API (case-by-case) public-releases
9 weeks

M4

Public-release APIs

M3 + 9 weeks

18

activities for M5 starts @ public-release PR for an API

  • Release Management: prepare and declare M5 - meta-release availability
  • TSC: approve meta-release for M5
2 weeks

M5

Meta-releaseM4 + 2 weeks20
activities for M6 start @ M5
  • Commonalities & ICM: assess meta-release and provide feedback
  • API Sub Groups: assess meta-release and provide feedback
  • Release Management: assess meta-release, create improvement plan and declare M6 - post-release assessment available
  • TSC: approve improvement plan for M6
2 weeks

M6

Post Release AssessmentM5 + 2 weeks24

Processes

All CAMARA teams play their part in the meta-release process. An overview of the activities per team is shown in the above table.

The details on the activities for each team can be found in the below process descriptions:

  • The process to manage a meta-release is described here: Meta-release Process
  • The process for the Commonalities and ICM teams is described here: Commonalities and ICM release process
  • Details on releasing an API version and the related API versioning are described here: API Release Process. 

...

  • Release of Commonalities.
  • Complete initial PR reviews.
  • TSC Approval.

...

  • Scope Request to Sub-Projects / APIs.
  • Determine requirements for sub-projects/APIs.
  • Determine requirements for sub-projects/APIs.
  • Create PRs for sub-projects/APIs.
  • Review and finalize PRs.
  • Confirm scope of sub-projects/APIs.
  • Identify release candidates for sub-projects/APIs.

...

  • Release of Sub-Projects / APIs.
  • Testing & Acceptance.
  • Conduct testing.
  • Evaluate acceptance criteria.
  • Code Freeze

...

  • Bundle & publish release
  • Common Release Date ("packaging done for the community release").

...

  • Review release process and identify areas for improvement. 
  • Release Retro.
    • Inputs from Sub Projects
  • TSC Approval.

...

Meta-release content planning

For each meta-release, the respective teams shall update the information of what they plan to contribute on the relevant meta-release page.

Commonalities & ICM

The Commonalities and ICM teams shall respectively update the related table as follows:

  • The version shall be updated with the latest pre-release version in use by the respective teams.
  • The actual Mx dates shall be put in the table when the milestone is passed. 
  • The link to the release package shall be added at M2 and is the same at M5.
  • When M2 is passed, the target public-release version shall be put in the Version column.

APIs

API Sub-project teams shall update the table for APIs as follows: 

  • The version shall be updated with the latest pre-release API version in use by the team.
  • The actual Mx dates shall be put in the table when the milestone is passed. 
  • The link to the release package shall be added at M3, M4, and the final at M5.
  • When M5 is passed, the target public-release API version shall be put in the Version column.