Skip to content

Replace group::memory to group::application performance in FFs

What does this MR do and why?

Our team was renamed. We need to update our existing :ops FFs accordingly.

Note that I haven't touched config/feature_flags/development/ci_register_job_temporary_lock.yml. The discussion is at #323180 (comment 1193289235). It will likely needs to be grouppipeline execution and converted to :ops or even removed entirely.

We discussed dynamic_image_resizing FF and the feature ownership in Slack.

We could drop these flags in a follow-up:

  • gitlab_service_measuring_projects_create_service
  • gitlab_service_measuring_projects_import_export_export_service
  • gitlab_service_measuring_projects_import_service

Discussed in #383565 (comment 1193273926). To start, let's correct the group label.

How to set up and validate locally

N/A, only changes FFs label data and docs

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #383565 (closed)

Edited by Aleksei Lipniagov

Merge request reports

Loading