You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

WIP

Introduction

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

Overview

CAMARA releases is scheduled to twice per year at approximately 6 month intervals (May and November). Releases are named after major world cities in alphabetical order. See the CAMARA Release Roadmap for a list of previous and future releases.

Releases are administered and tracked by a Community Release Managers. Release status is discussed at the << TBC >>

Release Milestones

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

MilestoneMilestone NameDescriptionTimeline
Kickoff - M0Start of release cycle.
M0
M1Initiate Commonalities & ICM
  • Scope of Work Products clarified.
  • Identify commonalities work products.
  • Create initial PRs for commonalities.
  • Agree on the scope of commonalities.
  • TSC Approval.
M0 + 2 week
M2Finalize Commonalities & ICM
  • Release of Commonalities.
  • Complete initial PR reviews.
  • TSC Approval.
M1 + 7 weeks
M3Initiate Sub-Projects / APIs
  • 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.
M1 + 6 weeks
 M4Finalize Sub-projects / APIs
  • Release of Sub-Projects / APIs.
  • Testing & Acceptance.
  • Conduct testing.
  • Evaluate acceptance criteria.
  • Code Freeze
M3 + 8 weeks
M5Meta Release
  • Bundle & publish release
  • Common Release Date ("packaging done for the community release").
M4 + 2 weeks
M6Post- Release
  • Review release process and identify areas for improvement. 
  • Release Retro.
    • Inputs from Sub Projects
  • TSC Approval.
M5 + 2 weeks


....................................


  • No labels