summaryrefslogtreecommitdiff
path: root/doc/development/deprecation_guidelines/index.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/deprecation_guidelines/index.md')
-rw-r--r--doc/development/deprecation_guidelines/index.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/development/deprecation_guidelines/index.md b/doc/development/deprecation_guidelines/index.md
index 07a29b17ddc..3543345aa34 100644
--- a/doc/development/deprecation_guidelines/index.md
+++ b/doc/development/deprecation_guidelines/index.md
@@ -14,8 +14,7 @@ changes to GitLab features.
It's important to understand the difference between **deprecation** and
**removal**:
-**Deprecation** is the process of flagging/marking/announcing that a feature
-is scheduled for removal in a future version of GitLab.
+**Deprecation** is the process of flagging/marking/announcing that a feature is no longer fully supported and may be removed in a future version of GitLab.
**Removal** is the process of actually removing a feature that was previously
deprecated.
@@ -31,7 +30,7 @@ Deprecations should be announced via [release posts](https://about.gitlab.com/ha
Generally, feature or configuration can be removed/changed only on major release.
It also should be [deprecated in advance](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations).
-For API removals, see the [GraphQL](../../api/graphql/index.md#deprecation-and-removal-process) and [GitLab API](../../api/README.md#compatibility-guidelines) guidelines.
+For API removals, see the [GraphQL](../../api/graphql/index.md#deprecation-and-removal-process) and [GitLab API](../../api/index.md#compatibility-guidelines) guidelines.
For configuration removals, see the [Omnibus deprecation policy](https://docs.gitlab.com/omnibus/package-information/deprecation_policy.html).