Rollout new_model_selection feature flag
Summary
Roll out the feature currently behind the new_model_selection feature flag.
- DRI: @nickleonard
- Team Slack channel:
#f_web-chat
Note
Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. Feature flag controls · Feature flag lifecycle
What could go wrong?
UI refresh, primarily UX concerns
Events
- Exceptions with :1
- Events with :1
- Error rate and other graphs by modifying the examples in the Visualization Library
Feature Flag events are only logged by default for feature flags marked for the current or future milestones. To enable while the feature flag is active, see https://docs.gitlab.com/development/feature_flags/#logging
Rollout
Run all production /chatops in #production and cross-post the results to #<slack-channel-of-dri-team>. Background: incremental rollout process, feature actors.
Non-production
/chatops gitlab run feature set <feature-flag-name> 50 --actors --dev --pre --staging --staging-ref
/chatops gitlab run feature set <feature-flag-name> true --dev --pre --staging --staging-refProduction — percentage rollout (wait ≥15 min between steps, watch dashboards):
/chatops gitlab run feature set <feature-flag-name> <percentage> --actorsOr target specific actors instead:
/chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss <feature-flag-name> true
/chatops gitlab run feature set --group=gitlab-org,gitlab-com <feature-flag-name> true
/chatops gitlab run feature set --user=<gitlab-username-of-dri> <feature-flag-name> trueBefore global rollout
Confirm the relevant gotchas before going to 100% — see enabling a feature for GitLab.com:
- Docs + version history updated
- Breaking changes announced, if any
- Change management issue opened, if required
- External API consumers handled with a fail-open mechanism, if applicable
Cleanup
Remove the flag once deemed stable — see cleaning up. Track it here, or open a follow-up Feature Flag Cleanup issue. Remove the flag and its YAML definition from the codebase, then:
/chatops gitlab run release check <merge-request-url> <milestone>
/chatops gitlab run feature delete <feature-flag-name> --dev --pre --staging --staging-ref --productionRollback
/chatops gitlab run feature set <feature-flag-name> false # production
/chatops gitlab run feature set <feature-flag-name> false --dev --pre --staging --staging-ref # non-production
/chatops gitlab run feature delete <feature-flag-name> --dev --pre --staging --staging-ref --production # remove entirely