Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 100
-
Issues for the Build team. Covers everything related to the GitLab omnibus package: https://gitlab.com/gitlab-org/omnibus-gitlab
-
Issues for the CI/CD team. Covers everything related to GitLab CI, including Deploy, Pages and the container registry
-
Issues that have been scheduled for an upcoming release and are actively being worked on by people from the community
-
Feature proposals or bug reports, collected by developer advocates
-
Issues for the Discussion team. Covers Issues, Merge Requests, Markdown, etc
-
Issues for the Documentation team. Covers our efforts to continuously improve and maintain the quality of GitLab documentation
-
Features or changes limited or intended as part of EE Premium. For GitLab.com, corresponds to any non-admin features in the Silver and Gold Plans https://about.gitlab.com/gitlab-com/
-
Issues for the Edge team. Covers GitLab code/workflows improvements, Triaging issues, Reviewing Community MRs, etc
-
Issues for the Geo team. See http://doc.gitlab.com/ee/gitlab-geo/README.html
-
Issues that are undergoing code review by the development team and/or undergoing design review by the UX team
-
Issues to put in the next patch release. Work on these first, and add the Pick Into Stable label to the merge request, along with the appropriate milestone.