Labels

Merge requests which are ready to be reviewed and can be reviewed by any team-member with sufficient knowledge in the given area. For reviewing the merge request just assign to yourself and remove this label.

Issues that need further input from team members in order for it to be "workflow::ready for development" https://handbook.gitlab.com/handbook/product-development-flow/#build-phase-1-plan

Issues that are ready for development but are not yet active (or have an associated release) https://handbook.gitlab.com/handbook/product-development-flow/#description-4

Workflow label for validating that the proposed solution meets user needs https://handbook.gitlab.com/handbook/product-development-flow/#validation-phase-4-solution-validation

Merge request has been deployed to staging.gitlab.com.

Merge request is deployed to the staging canary environment.

Merge request is deployed to the staging ref environment.

The entry point for workflow scoped labels. From here, Issues will either move through the validation workflow, go directly to planning and scheduling, or in certain cases, go directly to the development steps.

Testing per #771

Issues in a backlog of potential validation opportunities. This label is part of the product development flow https://handbook.gitlab.com/handbook/product-development-flow/#workflow-summary

Everything has been merged, waiting for verification after a deploy https://handbook.gitlab.com/handbook/product-development-flow/#description-5

Successfully completed the current version (experimental or beta) and promoted to the next version (beta or GA). See https://docs.gitlab.com/ee/policy/alpha-beta-support.html

Issues on both the GitLab Workhorse and GitLab CE projects

Remote Development Workspaces issues which have already been closed in previous iterations

Label tracking work needed for Project Zero Console (gitlab-com/gl-infra&1426)