[Feature flag] Enable CTE-based epic aggregates
What
Remove the :unfiltered_epic_aggregates
feature flag. Switch on CTE-based (faster) epic aggregates permanently.
Owners
- Team: Plan:Portfolio Management
- Most appropriate slack channel to reach out to:
#g_plan
- Best individual to reach out to: @cablett or @jprovaznik
Expectations
### What are we expecting to happen?
There is no problems and everyone enjoys super-fast epic counts and weight sums
What might happen if this goes wrong?
Hopefully we'll have enough data points with larger epic trees to put sensible limits in place (see #208607 and !23406 (comment 297901409)
What can we monitor to detect problems with this?
Perhaps watching timeouts loading epic trees
Beta groups/projects
If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.
-
gitlab-org/gitlab
project -
gitlab-org
/gitlab-com
groups
Roll Out Steps
-
Enable on staging -
Test on staging -
Ensure that documentation has been updated -
Enable on GitLab.com for individual groups/projects listed above and verify behaviour -
Coordinate a time to enable the flag with #production
and#g_delivery
on slack. -
Announce on the issue an estimated time this will be enabled on GitLab.com -
Enable on GitLab.com by running chatops command in #production
-
Cross post chatops slack command to #support_gitlab-com
and in your team channel -
Announce on the issue that the flag has been enabled -
Remove feature flag and add changelog entry -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel