• A CAMARA meta-release combines a set of CAMARA API versions into a consistent release.
• There are two meta-releases per year (in spring and fall).
  • API providers (e.g. Network operators, Channel Partners) can plan their implementations and deployments in production.
  • API consumers can plan the integration in their platform and applications.
• All API versions in a meta-release fulfill defined quality criteria and are compliant to the CAMARA guidelines from CAMARA Commonalities and Identity and Consent Management of that meta-release.
• CAMARA meta-releases ensure the
  • Availability of consistent API definitions (by use of guidelines, templates, and linting),
  • Quality of API definitions (by use of checklists, test definitions, and release management),
  • Stability of API definitions (clear criteria for stable versus initial API versions) and
  • Reliability of schedule and deliverables (with defined milestones and release candidates).
• CAMARA meta-releases provide the foundation for API version management in production.

For details see
https://wiki.camaraproject.org/display/CAM/Meta-release+Process.

2 meta-releases per Year

• Fall (in September)
• Spring (in March)

Continuous and Overlapping Cycles

• Update of CAMARA guidelines
• Development and updates of API definitions in CAMARA
• Lab implementations and production deployments at network operators

Tests of API Release Candidates

• In (operator) lab implementations
• Based on CAMARA test definitions

Feedback in All Phases

• From (lab) implementations and deployments to CAMARA API definitions and guidelines
• From API definition work to
  CAMARA guidelines