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, 5 insertions, 0 deletions
diff --git a/doc/development/deprecation_guidelines/index.md b/doc/development/deprecation_guidelines/index.md
index 2d092b24d65..07a29b17ddc 100644
--- a/doc/development/deprecation_guidelines/index.md
+++ b/doc/development/deprecation_guidelines/index.md
@@ -24,8 +24,13 @@ deprecated.
A feature can be deprecated at any time, provided there is a viable alternative.
+Deprecations should be announced via [release posts](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations).
+
## When can a feature be removed/changed?
+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 configuration removals, see the [Omnibus deprecation policy](https://docs.gitlab.com/omnibus/package-information/deprecation_policy.html).