diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-06-16 21:25:58 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-06-16 21:25:58 +0300 |
commit | a5f4bba440d7f9ea47046a0a561d49adf0a1e6d4 (patch) | |
tree | fb69158581673816a8cd895f9d352dcb3c678b1e /.gitlab/issue_templates | |
parent | d16b2e8639e99961de6ddc93909f3bb5c1445ba1 (diff) |
Add latest changes from gitlab-org/gitlab@14-0-stable-eev14.0.0-rc42
Diffstat (limited to '.gitlab/issue_templates')
5 files changed, 19 insertions, 29 deletions
diff --git a/.gitlab/issue_templates/Documentation.md b/.gitlab/issue_templates/Documentation.md index f05d7049b7f..c58b6d0cf06 100644 --- a/.gitlab/issue_templates/Documentation.md +++ b/.gitlab/issue_templates/Documentation.md @@ -25,7 +25,7 @@ * Include use cases, benefits, and/or goals for this work. * If adding content: What audience is it intended for? (What roles and scenarios?) For ideas, see personas at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ or the persona labels at - https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A + https://gitlab.com/groups/gitlab-org/-/labels?subscribed=&search=persona%3A --> ### Proposal diff --git a/.gitlab/issue_templates/Feature Flag Removal.md b/.gitlab/issue_templates/Feature Flag Removal.md deleted file mode 100644 index c061ab8516c..00000000000 --- a/.gitlab/issue_templates/Feature Flag Removal.md +++ /dev/null @@ -1,28 +0,0 @@ -<!-- Title suggestion: [Feature flag] Remove FEATURE_FLAG_NAME --> - -## Feature - -The `:feature_name` feature flag was previously [enabled by default](URL) and should be removed. - -## Owners - -- Group: ~"group::GROUP_NAME" -- Slack channel: `#g_GROUP_NAME` -- DRI: USERNAME -- PM: USERNAME - -**Removal** - -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). - -- [ ] Remove `:feature_name` 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 some_feature`. - -- [ ] Close this issue after the feature flag is removed from the codebase. - -/label ~"feature flag" ~"technical debt" -/assign DRI diff --git a/.gitlab/issue_templates/Feature Flag Roll Out.md b/.gitlab/issue_templates/Feature Flag Roll Out.md index f07604d2d3d..424b752d1b4 100644 --- a/.gitlab/issue_templates/Feature Flag Roll Out.md +++ b/.gitlab/issue_templates/Feature Flag Roll Out.md @@ -110,6 +110,12 @@ To do so, follow these steps: the feature can be officially announced in a release blog post. - [ ] `/chatops run auto_deploy status <merge-commit>` - [ ] Close [the feature issue](ISSUE LINK) to indicate the feature will be released in the current milestone. +- [ ] Set the next milestone to this rollout issue for scheduling [the flag removal](#release-the-feature). +- [ ] (Optional) You can create a separate issue for scheduling the steps below to [Release the feature](#release-the-feature). + - [ ] Set the title to "[Feature flag] Cleanup `<feature-flag-name>`". + - [ ] Execute the `/copy_metadata <this-rollout-issue-link>` quick action to copy the labels from this rollout issue. + - [ ] Link this rollout issue as a related issue. + - [ ] Close this rollout issue. **WARNING:** This approach has the downside that it makes it difficult for us to [clean up](https://docs.gitlab.com/ee/development/feature_flags/controls.html#cleaning-up) the flag. diff --git a/.gitlab/issue_templates/Geo Replicate a new Git repository type.md b/.gitlab/issue_templates/Geo Replicate a new Git repository type.md index feabef36f20..be6fef40f3a 100644 --- a/.gitlab/issue_templates/Geo Replicate a new Git repository type.md +++ b/.gitlab/issue_templates/Geo Replicate a new Git repository type.md @@ -513,6 +513,12 @@ That's all of the required database changes. last_synced_at { 1.day.ago } retry_count { 0 } end + + trait :verification_succeeded do + verification_checksum { 'e079a831cab27bcda7d81cd9b48296d0c3dd92ef' } + verification_state { Geo::CoolWidgetRegistry.verification_state_value(:verification_succeeded) } + verified_at { 5.days.ago } + end end end ``` diff --git a/.gitlab/issue_templates/Geo Replicate a new blob type.md b/.gitlab/issue_templates/Geo Replicate a new blob type.md index b9e69d36ecc..c7bbb6b937c 100644 --- a/.gitlab/issue_templates/Geo Replicate a new blob type.md +++ b/.gitlab/issue_templates/Geo Replicate a new blob type.md @@ -479,6 +479,12 @@ That's all of the required database changes. last_synced_at { 1.day.ago } retry_count { 0 } end + + trait :verification_succeeded do + verification_checksum { 'e079a831cab27bcda7d81cd9b48296d0c3dd92ef' } + verification_state { Geo::CoolWidgetRegistry.verification_state_value(:verification_succeeded) } + verified_at { 5.days.ago } + end end end ``` |