Create labels for the new ecosystem stage
Summary
This template is for the following types of label changes
- Adding a new Stage or Group
- Renaming an existing Stage or Group
For every case above, the Engineering Productivity team needs to ensure that:
- The label change is factored into the triage mechanism.
- Engineering Dashboards at https://quality-dashboard.gitlap.com/groups/gitlab-org are updated.
- Old labels are migrated correctly on affected issues and merge requests.
With gitlab-com/www-gitlab-com!86129 (merged) group::ecosystem became a stage.
This means that effectively all group::ecosystem issues should become devops::ecosystem issues. We have three groups that belong to ecosystem:
-
group::integrations(aligns withCategory:Integrations) -
group::foundations(aligns withCategory:FE/UX Foundations, which should be renamed toCategory:Foundations(done in #719 (closed))) -
group::contributor experience(aligns with the GDK)
Action items
-
(If applicable) Dashboard creation: create or update the stage/group in https://gitlab.com/gitlab-org/gitlab-insights/blob/master/lib/gitlab_insights.rb. -
(If applicable) Label migration on existing issues and merge requests: apply the new label to opened & closed issues, and open & merged merge requests. -
(If applicable) Archive the old label with renaming and adding "DEPRECATED" at the end of the label name. groupecosystem [DEPRECATED] -
(If applicable) Delete the old dashboard views using the deprecated labels. -
(If applicable) Update the group triage report definition to use the new label. !903 (merged) -
(If applicable) Update the group label's description to refer to the new Stage: -
Update renovate-gitlab-bot gitlab-org/frontend/renovate-gitlab-bot!495 (merged) -
Tanuki Stan considerations gitlab-org/ml-ops/tanuki-stan#2 (closed) -
SiSense update https://gitlab.com/gitlab-data/analytics/-/issues/10346
Edited by Arturo Herrero