Skip to content

[Clean up] role_targeted_broadcast_messages

Summary

This issue is to cleanup the role_targeted_broadcast_messages feature flag but KEEP THE BEHAVIOUR. It has been rolled out for over a year. According to @eugielimpin this was not an experiment #351736 (comment 1323051755)

Original issue: gitlab-org/growth/team-tasks#461 (closed)

Owners

  • Team: g_activation
  • Most appropriate slack channel to reach out to: #g_activation
  • Best individual to reach out to: @p_cordero (originally @jstava)
  • PM: @p_cordero

Stakeholders

Expectations

What might happen if this goes wrong?

Cleaning up the feature flag

  • Create a merge request to remove <feature-flag-name> 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 <feature-flag-name> --dev
    • /chatops run feature delete <feature-flag-name> --staging
    • /chatops run feature delete <feature-flag-name>
  • Close this rollout issue.