## What Enable by default, and then ultimately remove the `:use_smooshpack_fork` feature flag. This flag is used to load a [fork of our codesandbox package](https://gitlab.com/pslaughter/gitlab-codesandbox-client) which contains [pending upstream changes](https://github.com/codesandbox/codesandbox-client/pull/5137). ## Owners - Team: ~"group::editor" - Most appropriate slack channel to reach out to: `#g_create_editor` - Best individual to reach out to: @pslaughter ## Expectations ### What are we expecting to happen? ### What might happen if this goes wrong? ### What can we monitor to detect problems with this? <!-- Which dashboards from https://dashboards.gitlab.net are most relevant? Sentry errors reports can alse be useful to review --> ## 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 - [ ] Confirm that QA tests pass with the feature flag enabled (if you're unsure how, contact the relevant [stable counterpart in the Quality department](https://about.gitlab.com/handbook/engineering/quality/#individual-contributors)) - [ ] Enable on staging (`/chatops run feature set feature_name true --staging`) - [ ] Test on staging - [ ] Ensure that documentation has been updated - [ ] Enable on GitLab.com for individual groups/projects listed above and verify behaviour (`/chatops run feature set --project=gitlab-org/gitlab feature_name true`) - [ ] Coordinate a time to enable the flag with the SRE oncall and release managers - In `#production` mention `@sre-oncall` and `@release-managers`. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout - [ ] Announce on the issue an estimated time this will be enabled on GitLab.com - [ ] Enable on GitLab.com by running chatops command in `#production` (`/chatops run feature set feature_name true`) - [ ] Cross post chatops Slack command to `#support_gitlab-com` ([more guidance when this is necessary in the dev docs](https://docs.gitlab.com/ee/development/feature_flags/controls.html#where-to-run-commands)) 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](https://docs.gitlab.com/ee/development/feature_flags/controls.html#cleaning-up) by running chatops command in `#production` channel ## Rollback Steps - [ ] This feature can be disabled by running the following Chatops command: ``` /chatops run feature set --project=gitlab-org/gitlab feature_name false ```