[Feature flag] Cleanup track_semver_dialect_errors_for_cvs_in_sentry

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

This issue is to cleanup the track_semver_dialect_errors_for_cvs_in_sentry OPS feature flag.

This OPS flag was introduced to prevent flooding sentry with alerts. This allows the groupcomposition analysis team to temporarily enable the error reporting to investigate some issues and address them without spamming the alert system. See #481980 (closed).

According to the 12 months lifespan guideline, we should remove this flag by %18.4.

Owners

• Team :groupcomposition analysis
• Most appropriate slack channel to reach out to: #g_secure-composition-analysis
• Best individual to reach out to: @gonzoyumo
• PM: @johncrowley

Stakeholders

Expectations

What might happen if this goes wrong?

Sentry will be flooded with alerts.

We should have completed #464007 before removing this FF, making most of the user generated errors reported directly to the UI rather than in sentry.

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 <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 --pre --staging --staging-ref --production
• Close this rollout issue.