Phases to achieve Cells 1.0

As discussed in the Cells Cross-functional Sync call, we determined that having phases that make up the Cells 1.0 delivery would make it easier to understand the order of work to achieve the goal of having a new Cell in production.

The purpose of this issue is to decide on these phases so that they can be included in the Infrastructure Blueprint.

Scope:

  • Alignment of the distinct phases required to Deliver Cells 1.0
  • Assignment of High level items in Cell Schedule to phases

Exit Criteria

  • Aligned Phases in this issue
  • Owner for each Phase
  • High level items in cell schedule assigned to phases
  • This information included in Cells Infrastructure Blueprint

QA Cell

Production Cell 1 (Experimental)

Stage owner: @rnienaber

  1. See readiness review for experimental state: https://gitlab.com/gitlab-com/gl-infra/readiness/-/blob/master/.gitlab/issue_templates/production_readiness.md?ref_type=heads#experiment
  2. This phase is completed when a cell exists in production with one internal project and the internal project covers all cases necessary for testing.

Production Cell 1 (Beta)

Stage owner: @rnienaber

  1. See readiness review for beta state: https://gitlab.com/gitlab-com/gl-infra/readiness/-/blob/master/.gitlab/issue_templates/production_readiness.md?ref_type=heads#beta
  2. This phase is complete when the work to upgrade from experimental to beta (described in the review document) are completed.
  3. If a customer wants to participate in this stage, the guarantees of Beta apply.

Production Cell 1 (GA)

Stage owner: @rnienaber

  1. See readiness review for general-availability state: https://gitlab.com/gitlab-com/gl-infra/readiness/-/blob/master/.gitlab/issue_templates/production_readiness.md?ref_type=heads#general-availability
  2. This phase is complete when the work to upgrade from beta to generally-available (described in the review document) are completed.

Action Items

Edited by Rachel Nienaber