Labels

Changes to .gitlab/CODEOWNERS

This is a "must have" item for our release to GA

This is a "should have" item for our release to GA

This is a "nice to have" for our release to GA

Used to denote an issue which will impact Commercial customers. Typically added if repeatedly seen by the Commercial Sales team.

The sole purpose of this label is to communicate common bugs that the Provision Team have identified. This could probably be replaced by a more complex search using a combination of type::bug, priority::1, etc. when &291 is completed

Use this label to alert the Community Relations team of any changes expected to have a meaningful impact on the wider GitLab community or the GitLab brand

Issues related to complimentary subscriptions to GitLab Ultimate for program participants.

Key issues to highlight for the wider community. Community members will receive a GitLab merchandise when an MR is merged.

Issues that have been scheduled for an upcoming release and are actively being worked on by our community

Community response actions (Developer Evangelism)

Tracking the component maturity efforts in the design system

Issues related to counting of Compute minutes and calculation of usage

RICE Framework - confidence is 100%. https://about.gitlab.com/handbook/product/product-processes/#using-the-rice-framework

RICE Framework - confidence is 50%. https://about.gitlab.com/handbook/product/product-processes/#using-the-rice-framework

RICE Framework - confidence is 80%. https://about.gitlab.com/handbook/product/product-processes/#using-the-rice-framework

Issues related with the Container Registry upgrade/migration (&5523)

Issues that are blockers for the Container Registry upgrade/migration (&5523)

Issues related with the Container Registry upgrade/migration (&5523) that were not part of the original plan.