diff options
Diffstat (limited to 'data/deprecations')
12 files changed, 98 insertions, 49 deletions
diff --git a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml index 9e02524b022..28e58a0c60d 100644 --- a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml +++ b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml @@ -1,11 +1,11 @@ - name: "NFS for Git repository storage" # The name of the feature to be deprecated announcement_milestone: "14.0" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-06-22" # The date of the milestone release when this feature was first announced as deprecated - removal_milestone: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format - the date of the milestone release when this feature is planned to be removed - breaking_change: true + removal_milestone: "15.6" # The milestone when this feature is planned to be removed + removal_date: "2022-11-22" # (optional - may be required in the future) YYYY-MM-DD format - the date of the milestone release when this feature is planned to be removed + breaking_change: false body: | # Do not modify this line, instead modify the lines below. - With the general availability of Gitaly Cluster ([introduced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/)), we have deprecated development (bugfixes, performance improvements, etc) for NFS for Git repository storage in GitLab 14.0. We will continue to provide technical support for NFS for Git repositories throughout 14.x, but we will remove all support for NFS in GitLab 15.0. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for further information. + With the general availability of Gitaly Cluster ([introduced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/)), we have deprecated development (bugfixes, performance improvements, etc) for NFS for Git repository storage in GitLab 14.0. We will continue to provide technical support for NFS for Git repositories throughout 14.x, but we will remove all support for NFS on November 22, 2022. This was originally planned for May 22, 2022, but in an effort to allow continued maturity of Gitaly Cluster, we have chosen to extend our deprecation of support date. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for further information. Gitaly Cluster offers tremendous benefits for our customers such as: @@ -15,7 +15,8 @@ We encourage customers currently using NFS for Git repositories to plan their migration by reviewing our documentation on [migrating to Gitaly Cluster](https://docs.gitlab.com/ee/administration/gitaly/index.html#migrate-to-gitaly-cluster). - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + reporter: mjwood + stage: create # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth tiers: # (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] issue_url: # (optional) This is a link to the deprecation issue in GitLab documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml b/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml new file mode 100644 index 00000000000..e5646f5123d --- /dev/null +++ b/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml @@ -0,0 +1,9 @@ +- name: "Toggle notes confidentiality on APIs" + announcement_milestone: "14.10" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-03-22" # 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: "16.0" # The milestone when this feature is planned to be removed + removal_date: "2023-05-22" # 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: true # If this deprecation is a breaking change, set this value to true + body: | # Do not modify this line, instead modify the lines below. + Toggling notes confidentiality with REST and GraphQL APIs is being deprecated. Updating notes confidential attribute is no longer supported by any means. We are changing this to simplify the experience and prevent private information from being unintentionally exposed. + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/350670 diff --git a/data/deprecations/14-10-manual-iteration-management.yml b/data/deprecations/14-10-manual-iteration-management.yml new file mode 100644 index 00000000000..f677f4fe668 --- /dev/null +++ b/data/deprecations/14-10-manual-iteration-management.yml @@ -0,0 +1,34 @@ +- name: "Manual iteration management" # The name of the feature to be deprecated + announcement_milestone: "14.10" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-04-22" # 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: "16.0" # The milestone when this feature is planned to be removed + removal_date: "2023-04-22" # 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: true # If this deprecation is a breaking change, set this value to true + reporter: mcelicalderonG # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + Manual iteration management is deprecated and only automatic iteration cadences will be supported in the future. + + Creating and deleting iterations will be fully removed in 16.0. Updating all iteration fields except for + `description` will also be removed. + + On the GraphQL API the following mutations will be removed: + + 1. `iterationCreate` + 1. `iterationDelete` + + The update `updateIteration` mutation will only allow updating the iteration's `description`. The following + arguments will be removed: + + 1. `title` + 1. `dueDate` + 1. `startDate` + + For more information about iteration cadences, you can refer to + [the documentation of the feature](https://docs.gitlab.com/ee/user/group/iterations/#iteration-cadences). +# The following items are not published on the docs page, but may be used in the future. + stage: Plan + tiers: # (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] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/356069 + 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 diff --git a/data/deprecations/14-10-old-search-migration-removal.yml b/data/deprecations/14-10-old-search-migration-removal.yml new file mode 100644 index 00000000000..d7036150059 --- /dev/null +++ b/data/deprecations/14-10-old-search-migration-removal.yml @@ -0,0 +1,12 @@ +- name: "Outdated indices of Advanced Search migrations" + announcement_milestone: "14.10" + announcement_date: "2021-04-22" + removal_milestone: "15.0" + removal_date: "2021-05-22" + breaking_change: true + body: | + As Advanced Search migrations usually require support multiple code paths for a long period of time, it’s important to clean those up when we safely can. We use GitLab major version upgrades as a safe time to remove backward compatibility for indices that have not been fully migrated. See the [upgrade documentation](https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version) for details. + stage: enablement + tiers: premium, ultimate + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/359133 + documentation_url: https://docs.gitlab.com/ee/development/elasticsearch.html#deleting-advanced-search-migrations-in-a-major-version-upgrade diff --git a/data/deprecations/14-5-runner-api-status-does-contain-paused.yml b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml index 46f1ef89b53..5acfac45ca2 100644 --- a/data/deprecations/14-5-runner-api-status-does-contain-paused.yml +++ b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml @@ -1,11 +1,11 @@ - name: "REST and GraphQL API Runner status will not return `paused`" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" - removal_milestone: "15.0" # the milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed + removal_milestone: "16.0" # the milestone when this feature is planned to be removed + removal_date: "2023-04-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. - The GitLab Runner REST and GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 15.0. + The GitLab Runner REST and GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 16.0. A runner's status will only relate to runner contact status, such as: `online`, `offline`, or `not_connected`. Status `paused` or `active` will no longer appear. diff --git a/data/deprecations/14-8-ci-build-variables.yml b/data/deprecations/14-8-ci-build-variables.yml index 52c7ecf6c52..a87c6a2fa17 100644 --- a/data/deprecations/14-8-ci-build-variables.yml +++ b/data/deprecations/14-8-ci-build-variables.yml @@ -1,12 +1,27 @@ - name: "`CI_BUILD_*` predefined variables" announcement_milestone: "14.8" announcement_date: "2021-02-22" - removal_milestone: "15.0" - removal_date: "2022-05-22" + removal_milestone: "16.0" + removal_date: "2023-04-22" breaking_change: true reporter: dhershkovitch body: | - The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in GitLab 9.0, and will be removed in GitLab 15.0. If you still use these variables, be sure to change to the current [`CI_JOB_*` predefined variables](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html) which are identical (except for the updated name). + The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in GitLab 9.0, and will be removed in GitLab 16.0. If you still use these variables, be sure to change to the replacement [predefined variables](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html) which are functionally identical: + + | Removed variable | Replacement variable | + | --------------------- |------------------------ | + | `CI_BUILD_BEFORE_SHA` | `CI_COMMIT_BEFORE_SHA` | + | `CI_BUILD_ID` | `CI_JOB_ID` | + | `CI_BUILD_MANUAL` | `CI_JOB_MANUAL` | + | `CI_BUILD_NAME` | `CI_JOB_NAME` | + | `CI_BUILD_REF` | `CI_COMMIT_SHA` | + | `CI_BUILD_REF_NAME` | `CI_COMMIT_REF_NAME` | + | `CI_BUILD_REF_SLUG` | `CI_COMMIT_REF_SLUG` | + | `CI_BUILD_REPO` | `CI_REPOSITORY_URL` | + | `CI_BUILD_STAGE` | `CI_JOB_STAGE` | + | `CI_BUILD_TAG` | `CI_COMMIT_TAG` | + | `CI_BUILD_TOKEN` | `CI_JOB_TOKEN` | + | `CI_BUILD_TRIGGERED` | `CI_PIPELINE_TRIGGERED` | # The following items are not published on the docs page, but may be used in the future. stage: Verify tiers: [Free, Premium, Ultimate] diff --git a/data/deprecations/14-8-compliance-status-check-api-field.yml b/data/deprecations/14-8-compliance-status-check-api-field.yml index 5ad653c8fce..b98dab9e905 100644 --- a/data/deprecations/14-8-compliance-status-check-api-field.yml +++ b/data/deprecations/14-8-compliance-status-check-api-field.yml @@ -14,12 +14,12 @@ - Requests that have the `status` field set to `approved`. Beginning in GitLab 15.0, status checks will only be updated to a passing state if the `status` field is both present - and set to `pass`. Requests that: + and set to `passed`. Requests that: - Do not contain the `status` field will be rejected with a `422` error. For more information, see [the relevant issue](https://gitlab.com/gitlab-org/gitlab/-/issues/338827). - - Contain any value other than `pass` will cause the status check to fail. For more information, see [the relevant issue](https://gitlab.com/gitlab-org/gitlab/-/issues/339039). + - Contain any value other than `passed` will cause the status check to fail. For more information, see [the relevant issue](https://gitlab.com/gitlab-org/gitlab/-/issues/339039). - To align with this change, API calls to list external status checks will also return the value of `pass` rather than + To align with this change, API calls to list external status checks will also return the value of `passed` rather than `approved` for status checks that have passed. # The following items are not published on the docs page, but may be used in the future. stage: "Manage" diff --git a/data/deprecations/14-8-nfs_support.yml b/data/deprecations/14-8-nfs_support.yml deleted file mode 100644 index 534975b0642..00000000000 --- a/data/deprecations/14-8-nfs_support.yml +++ /dev/null @@ -1,28 +0,0 @@ -- name: "Reminder: support for NFS repository storage" # The name of the feature to be deprecated - announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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: true # If this deprecation is a breaking change, set this value to true - reporter: mjwood # GitLab username of the person reporting the deprecation - body: | # Do not modify this line, instead modify the lines below. - As [announced](https://about.gitlab.com/releases/2021/06/22/gitlab-14-0-released/#nfs-for-git-repository-storage-deprecated) at the - release of GitLab 14.0, technical support for NFS storage for Git repositories is being removed. Please see our official - [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for additional information. - - We encourage customers currently using NFS for Git repositories to plan their migration by reviewing our documentation on - [migrating to Gitaly Cluster](https://docs.gitlab.com/ee/administration/gitaly/#migrating-to-gitaly-cluster). - - Gitaly Cluster offers tremendous benefits for our customers such as: - - - [Variable replication factors](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#configure-replication-factor) - - [Strong consistency](https://docs.gitlab.com/ee/administration/gitaly/#strong-consistency) - - [Distributed read capabilities](https://docs.gitlab.com/ee/administration/gitaly/#distributed-reads) - -# The following items are not published on the docs page, but may be used in the future. - stage: Gitaly # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth - tiers: # (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] - issue_url: # (optional) This is a link to the deprecation issue in GitLab - 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 diff --git a/data/deprecations/14-9-deprecate-debian-9.yml b/data/deprecations/14-9-deprecate-debian-9.yml index 8f512393aa4..3dce4892ab7 100644 --- a/data/deprecations/14-9-deprecate-debian-9.yml +++ b/data/deprecations/14-9-deprecate-debian-9.yml @@ -4,4 +4,4 @@ removal_milestone: "15.1" removal_date: "2022-06-22" body: | - Long term service and support (LTSS) for [Debian 9 Stretch ends in July 2022](https://wiki.debian.org/LTS). Therefore, we will longer support the Debian 9 distribution for the GitLab package. Users can upgrade to Debian 10 or Debian 11. + Long term service and support (LTSS) for [Debian 9 Stretch ends in July 2022](https://wiki.debian.org/LTS). Therefore, we will no longer support the Debian 9 distribution for the GitLab package. Users can upgrade to Debian 10 or Debian 11. diff --git a/data/deprecations/14-9-system_monitoring.yml b/data/deprecations/14-9-system_monitoring.yml index 6c8dc61db4d..c4b3343bee6 100644 --- a/data/deprecations/14-9-system_monitoring.yml +++ b/data/deprecations/14-9-system_monitoring.yml @@ -1,12 +1,12 @@ -- name: "GitLab self-monitoring" # The name of the feature to be deprecated +- name: "GitLab self-monitoring project" # The name of the feature to be deprecated announcement_milestone: "14.9" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-03-22" # 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.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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. + removal_milestone: "16.0" # The milestone when this feature is planned to be removed + removal_date: "2023-05-22" # 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: true # If this deprecation is a breaking change, set this value to true reporter: abellucci # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. - GitLab self-monitoring gives administrators of self-hosted GitLab instances the tools to monitor the health of their instances. This feature is deprecated in GitLab 14.9, and is scheduled for removal in 15.0. + GitLab self-monitoring gives administrators of self-hosted GitLab instances the tools to monitor the health of their instances. This feature is deprecated in GitLab 14.9, and is scheduled for removal in 16.0. # The following items are not published on the docs page, but may be used in the future. stage: Monitor # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth tiers: [Core, Premium, 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] diff --git a/data/deprecations/15-0-deprecate-monitor-metrics.yml b/data/deprecations/15-0-deprecate-monitor-metrics.yml index f5fa63b9c40..9ad78d9c01d 100644 --- a/data/deprecations/15-0-deprecate-monitor-metrics.yml +++ b/data/deprecations/15-0-deprecate-monitor-metrics.yml @@ -1,8 +1,8 @@ - name: "Monitor performance metrics through Prometheus" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-22" # 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.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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: "16.0" # The milestone when this feature is planned to be removed + removal_date: "2023-05-22" # 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. breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. By displaying data stored in a Prometheus instance, GitLab allows users to view performance metrics. GitLab also displays visualizations of these metrics in dashboards. The user can connect to a previously-configured external Prometheus instance, or set up Prometheus as a GitLab Managed App. diff --git a/data/deprecations/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb index 1ef2af67a98..09a53404798 100644 --- a/data/deprecations/templates/_deprecation_template.md.erb +++ b/data/deprecations/templates/_deprecation_template.md.erb @@ -35,6 +35,12 @@ For deprecation reviewers (Technical Writers only): - For more information about updating the deprecation doc, see the deprecation doc update guidance: https://about.gitlab.com/handbook/marketing/blog/release-posts/#update-the-deprecations-doc --> + +View deprecations by the product versions in which they were announced. + +Each deprecation has a **planned removal milestone** and indicates whether it is a breaking change. + +Most of the deprecations are **planned for removal in 15.0**, and many of them are **breaking changes**. <% if milestones.any? -%> <%- milestones.each do |milestone| %> ## <%= milestone %> |