Labels
Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 4,347
-
changeGitLab.com / GitLab Infrastructure TeamAny change introduced to production that is not a deploy
-
changescheduledGitLab.com / GitLab Infrastructure TeamChange plans that are ready and scheduled for execution. See https://about.gitlab.com/handbook/engineering/infrastructure/change-management/.
-
chefGitLab.com / GitLab Infrastructure TeamThe guy that sets things on fire so we can eat them later
-
cincGitLab.com / GitLab Infrastructure TeamItems related to CINC configuration management infrastructure (open-source community supported distribution of Chef software)
-
closedstaleGitLab.comIssues that are being closed as inactive https://about.gitlab.com/handbook/engineering/quality/triage-operations/#auto-close-inactive-bugs
-
code-creation-triageneeds-reviewGitLab.comPart of the triage process for Create:Code Creation https://handbook.gitlab.com/handbook/engineering/development/dev/create/code-creation/milestone_planning/#planning-and-triage-process
-
code-creation-triagereviewedGitLab.comPart of the triage process for Create:Code Creation https://handbook.gitlab.com/handbook/engineering/development/dev/create/code-creation/milestone_planning/#planning-and-triage-process
-
cohort-0GitLab.com / GitLab Infrastructure TeamCohort 0 Test Cohort Up to 100 organizations Purpose: Validate the end-to-end transfer and migration process using test namespaces. Eligibility: None — test namespaces only. Exit criteria impact: Establishes baseline validation for subsequent cohorts.
-
cohort-AGitLab.com / GitLab Infrastructure TeamCohort A Subset of Inactive Free Users Up to 5,000 organizations Purpose: Establish Protocells in real production use and refine the migration process. Eligibility: Inactive root namespaces · Free plan · Private only. Exit criteria impact: Tiny impact on database size.
-
cohort-BGitLab.com / GitLab Infrastructure TeamCohort B Active Opt-in Beta Up to 1,000 organizations Purpose: Gain experience with real daily active users. Eligibility: Opt-in / guided · Active root namespaces · Free or paid · Private only. Exit criteria impact: Tiny impact on WAL, LWLocks and database size.
-
cohort-CGitLab.com / GitLab Infrastructure TeamCohort C — Top 1000 Opt-in Up to 300 organizations Purpose: Relieve the legacy cell. Eligibility: Opt-in / guided · Top 1,000 root namespaces by database time · Private only · Prerequisite: Feature parity. Exit criteria impact: At least 20% [1] decrease in WAL saturation and database size.
-
cohort-DGitLab.com / GitLab Infrastructure TeamCohort D Active Long Tail Opt-in Approximately 10,000 organizations Purpose: Relieve the legacy cell. Eligibility: Opt-in / self-service · Active root namespaces · Private only · Free or paid · Prerequisite: Feature parity. Exit criteria impact: At least 10% [2] decrease in WAL saturation and database size.
-
commit-design-editGitLab.comFor quick-turnaround, smaller edits that need to be made to existing design assets for Commit events