## Summary Roll out [the feature](https://gitlab.com/groups/gitlab-org/-/epics/2345) currently behind the `wiki_collaborative_editing` feature flag. - DRI: @leetickett-gitlab - Team Slack channel: `#g_planner-intelligence` > [!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](https://docs.gitlab.com/development/feature_flags/controls/) · [Feature flag lifecycle](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) ## What could go wrong? The main unknown is Redis memory. Each open wiki editing session holds a list of Yjs updates in `Gitlab::Redis::SharedState` for up to an hour, so concurrent editors on GitLab.com drive memory growth. That is the reason for a slow percentage ramp. - Redis SharedState memory and ops growth from per-document update lists — the primary scaling risk. - ActionCable connection load, since each editor holds an open websocket subscription. - Worst case for a user is a degraded editing session: lost or duplicated in-flight updates, or a fallback to non-collaborative editing. - No data-loss risk to the persisted wiki page. Saving still writes a normal Git commit, and the Redis log is ephemeral. - The flag actor is the current user, so ramping with `--actors` is meaningful. - Watch on https://dashboards.gitlab.net: Redis SharedState memory and ops, plus ActionCable / websocket connection counts. ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_planner-intelligence`. Background: [incremental rollout process](https://docs.gitlab.com/development/feature_flags/controls/#process), [feature actors](https://docs.gitlab.com/development/feature_flags/#feature-actors). **Non-production** ``` /chatops gitlab run feature set wiki_collaborative_editing 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set wiki_collaborative_editing true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set wiki_collaborative_editing 1 --actors /chatops gitlab run feature set wiki_collaborative_editing 10 --actors /chatops gitlab run feature set wiki_collaborative_editing 25 --actors /chatops gitlab run feature set wiki_collaborative_editing 50 --actors /chatops gitlab run feature set wiki_collaborative_editing 100 --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss wiki_collaborative_editing true /chatops gitlab run feature set --group=gitlab-org,gitlab-com wiki_collaborative_editing true /chatops gitlab run feature set --user=leetickett-gitlab wiki_collaborative_editing true ``` ## Before global rollout Confirm the relevant gotchas before going to 100% — see [enabling a feature for GitLab.com](https://docs.gitlab.com/development/feature_flags/controls/#enabling-a-feature-for-gitlabcom): - [Docs + version history](https://docs.gitlab.com/development/documentation/feature_flags/) updated - [Breaking changes](https://docs.gitlab.com/development/documentation/release_notes/#deprecations-removals-and-breaking-changes) announced, if any - [Change management issue](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#feature-flags-and-the-change-management-process) opened, if required - [External API consumers](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers) handled with a fail-open mechanism, if applicable ## Cleanup Remove the flag once [deemed stable](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) — see [cleaning up](https://docs.gitlab.com/development/feature_flags/controls/#cleaning-up). Track it here, or open a follow-up [Feature Flag Cleanup issue](https://gitlab.com/gitlab-org/gitlab/-/issues/new?description_template=Feature%20Flag%20Cleanup). Remove the flag and its YAML definition from the codebase, then: ``` /chatops gitlab run release check https://gitlab.com/gitlab-org/gitlab/-/merge_requests/250607 19.4 /chatops gitlab run feature delete wiki_collaborative_editing --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set wiki_collaborative_editing false # production /chatops gitlab run feature set wiki_collaborative_editing false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete wiki_collaborative_editing --dev --pre --staging --staging-ref --production # remove entirely ``` --- 🤖 *This content was generated by GitLab Duo.*