Skip to content

Roll out `:snippets_edit_vue` feature flag

What

After all parts and dependent issues of #38222 (closed) have been implemented behind the :snippets_edit_vue feature flag, we should roll this feature 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 Edit view of a Snippet should not change much. Some of the icons are supposed to look different (due to the use of gitlab-ui components).

What might happen if this goes wrong?

What can we monitor to detect problems with this?

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 not needed as there are no changes in the feature per se
  • 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
  • Enable the flag by default in the codebase

Note: the following steps belong to #220797 (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).

Edited by Denys Mishunov