Add a `database` category
Why is this change being made?
We use feature categories to attribute background Sidekiq workers, because feature categories are more stable than stages and groups. This adds a hidden (non-marketing, non-ROI) feature category for background migrations to allow us to assign the background_migrations
Sidekiq queue to it. Presently the Database group does not have any categories, so this MR introduces one named database
.
This attribution does not mean that the Database team are on the hook for all issues in background migrations, but that they will be the default point of contact for them (as they would be anyway) to triage them.
For gitlab-com/gl-infra/scalability#144 (closed).
Approvals
Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:
-
EVP of Product -
VP of Product Strategy -
The Product Director relevant to the stage group(s) -
The Engineering Director relevant to the stage group(s) -
CEO
The following people need to be on the merge request so they stay informed:
-
EVP of Engineering @edjdev
-
Senior Director of Development @clefelhocz1
-
Director of Quality @meks
-
The Product Marketing Manager relevant to the stage group(s)