diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-05-04 18:09:12 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-05-04 18:09:12 +0300 |
commit | 856e2c64ee69b055b31a8ebbeee616f13a46505e (patch) | |
tree | 0ec9b70c8f1f74516631bf87281c175e127fedd2 /data | |
parent | 8ed0a009f0ae0de789fae01b3cc9bda54aa03965 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'data')
-rw-r--r-- | data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml b/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml new file mode 100644 index 00000000000..271e11f0d7f --- /dev/null +++ b/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml @@ -0,0 +1,19 @@ +- name: "Vulnerability Report sort by State" # (required) The name of the feature to be deprecated + announcement_milestone: "15.0" # (required) The milestone when this feature was first announced as deprecated. + announcement_date: "2022-05-22" # (required) The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.2" # (required) The milestone when this feature is planned to be removed + removal_date: "2022-07-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: false # (required) If this deprecation is a breaking change, set this value to true + reporter: matt_wilson # (required) GitLab username of the person reporting the deprecation + stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/360516 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + The ability to sort the Vulnerability Report by the `State` column was disabled and put behind a feature flag in GitLab 14.10 due to a refactor + of the underlying data model. The feature flag has remained off by default as further refactoring will be required to ensure sorting + by this value remains performant. Due to very low usage of the `State` column for sorting, the feature flag will instead be removed in + GitLab 15.2 to simplify the codebase and prevent any unwanted performance degradation. +# The following items are not published on the docs page, but may be used in the future. + tiers: Ultimate # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] + documentation_url: # (optional) This is a link to the current documentation page + image_url: # (optional) This is a link to a thumbnail image depicting the feature + video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg |