Roll out `:monaco_ci` feature flag
What
After deploying Replace ACE with Editor Lite for /-/ci/lint
CI Linting behind the :monaco_ci
feature flag, the feature should be rolled out with the feature flag enabled by default. It is suggested to roll out globally to all users because the presence of the feature flag secures easy rollback should something go wrong.
Owners
- Team: Create::Editor (Frontend)
- Most appropriate slack channel to reach out to:
#g_create_editor
- Best individual to reach out to: @dmishunov
Expectations
What are we expecting to happen?
The CI linting view (/-/ci/lint
) should render Editor Lite (Monaco-based) instead of ACE
What might happen if this goes wrong?
Potential bugs in functionality that should either be addressed fast or the feature flag should be rolled back while it's available
Roll Out Steps
-
Enable on staging -
Test on staging -
Ensure that documentation has been updatednot needed as there are no changes in the feature per se -
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
The following step belongs to #198612 (closed)
-
Enable the flag by default in the codebase
The following steps belong to #198609 (closed)
-
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
Availability and Testing
Important: please run package-and-qa
job before the feature flag in enabled by default. Please also coordinate your changes with the SET (@a_mcdonald) as some further refactoring will need to be implemented as soon as the ff is enabled (see https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/492#note_335592893).