[Feature flag] Cleanup highlight_js_worker
Summary
This issue is to cleanup the highlight_js_worker
feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
Owners
- Team: groupsource code
- Most appropriate slack channel to reach out to:
#g_create_source-code-fe
- Best individual to reach out to: @jerasmus
Expectations
What are we expecting to happen?
As a result of this, all content would be highlighted upfront as opposed to highlighting in chunks which should contribute to more accurate highlighting in certain scenarios (read the description of #366531 (closed) to find out about the technical downsides of highlighting in chunks).
What might happen if this goes wrong?
Highlighting of Source Code might not work as expected.
What can we monitor to detect problems with this?
Consider mentioning checks for 5xx errors or other anomalies like an increase in redirects (302 HTTP response status)
Cleaning up the feature flag
-
Specify in the issue description if this feature will be removed completely or will be productized as part of the Feature Flag cleanup -
Create a merge request to remove highlight_js_worker
feature flag. Ask for review and merge it.-
Remove all references to the feature flag from the codebase. -
Remove the YAML definitions for the feature from the repository. -
Create a changelog entry.
-
-
Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post. -
/chatops run auto_deploy status <merge-commit-of-cleanup-mr>
-
-
Close the feature issue to indicate the feature will be released in the current milestone. -
If not already done, clean up the feature flag from all environments by running these chatops command in #production
channel:/chatops run feature delete highlight_js_worker --dev --ops --pre --staging --staging-ref --production
-
Close this rollout issue.
Edited by Jacques Erasmus