<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Collaborate/take over this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=328421) </details> <!--IssueSummary end--> <!-- Title suggestion: [Feature flag] Enable description of feature --> ## Feature This feature uses the `:cache_home_panel` feature flag! <!-- Short description of what the feature is about and link to relevant other issues. --> - [Cache parts of the home_panel partial](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/57031) ## Owners - Team: ~"group::source code" - Most appropriate slack channel to reach out to: `#g_create_source-code-be` - Best individual to reach out to: @robotmay_gitlab - PM: @danielgruesso ## The Rollout Plan - Partial Rollout on GitLab.com with beta groups - Rollout on GitLab.com for a certain period (How long) - Percentage Rollout on GitLab.com - Rollout Feature for everyone as soon as it's ready <!-- Which dashboards from https://dashboards.gitlab.net are most relevant? Sentry errors reports can also be useful to review --> https://dashboards.gitlab.net/d/web-rails-controller/web-rails-controller?orgId=1 **Beta Groups/Projects:** <!-- If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example. --> - `gitlab-org/gitlab` project - `gitlab-org`/`gitlab-com` groups ## Expectations ### What are we expecting to happen? <!-- Describe the expected outcome when rolling out this feature --> - Response time for the project homepage should improve ### What might happen if this goes wrong? <!-- Should the feature flag be turned off? Any MRs that need to be rolled back? Communication that needs to happen? What are some things you can think of that could go wrong - data loss or broken pages? --> - Project homepages could start throwing errors ### What can we monitor to detect problems with this? <!-- Which dashboards from https://dashboards.gitlab.net are most relevant? --> - Sentry - https://dashboards.gitlab.net/d/web-rails-controller/web-rails-controller?orgId=1 ## Rollout Timeline <!-- Please check which steps are needed and remove those which don't apply --> **Initial Rollout** *Preparation Phase* - [x] Enable on staging (`/chatops run feature set cache_home_panel true --staging`) - [x] Test on staging - [ ] Announce on the issue an estimated time this will be enabled on GitLab.com *Partial Rollout Phase* - [x] Enable on GitLab.com for individual groups/projects listed above and verify behaviour (`/chatops run feature set --project=gitlab-org/gitlab cache_home_panel true`) - [x] Verify behaviour (See Beta Groups) and add details with screenshots as a comment on this issue - [x] If it is possible to perform an incremental rollout, this should be preferred. Proposed increments are: `10%`, `50%`, `100%`. Proposed minimum time between increments is 15 minutes. - When setting percentages, make sure that the feature works correctly between feature checks. See https://gitlab.com/gitlab-org/gitlab/-/issues/327117 for more information - For actor-based rollout: `/chatops run feature set cache_home_panel 10 --actors` - For time-based rollout: `/chatops run feature set cache_home_panel 10` - [ ] Make the feature flag enabled by default i.e. Change `default_enabled` to `true` - [ ] Cross post chatops slack command to `#support_gitlab-com` ([more guidance when this is necessary in the dev docs](https://docs.gitlab.com/ee/development/feature_flags/controls.html#where-to-run-commands)) and in your team channel **Cleanup** This is an __important__ phase, that should be either done in the next Milestone or as soon as possible. For the cleanup phase, please follow our documentation on how to [clean up the feature flag](https://docs.gitlab.com/ee/development/feature_flags/controls.html#cleaning-up). <!-- The checklist here is to keep track of it's status for stakeholders --> - [ ] Announce on the issue that the flag has been enabled - [ ] Remove `:cache_home_panel` feature flag - [ ] Remove all references to the feature flag from the codebase - [ ] Remove the YAML definitions for the feature from the repository - [ ] Create a Changelog Entry - [ ] Clean up the feature flag from all environments by running this chatops command in `#production` channel `/chatops run feature delete cache_home_panel`. **Final Step** - [ ] Close this rollout issue for the feature flag after the feature flag is removed from the codebase. ## Rollback Steps - [ ] This feature can be disabled by running the following Chatops command: ``` /chatops run feature set --project=gitlab-org/gitlab cache_home_panel false ```