summaryrefslogtreecommitdiff
path: root/doc/development/deprecation_guidelines
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-08-20 18:42:06 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-08-20 18:42:06 +0000
commit6e4e1050d9dba2b7b2523fdd1768823ab85feef4 (patch)
tree78be5963ec075d80116a932011d695dd33910b4e /doc/development/deprecation_guidelines
parent1ce776de4ae122aba3f349c02c17cebeaa8ecf07 (diff)
downloadgitlab-ce-6e4e1050d9dba2b7b2523fdd1768823ab85feef4.tar.gz
Add latest changes from gitlab-org/gitlab@13-3-stable-ee
Diffstat (limited to 'doc/development/deprecation_guidelines')
-rw-r--r--doc/development/deprecation_guidelines/index.md23
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/development/deprecation_guidelines/index.md b/doc/development/deprecation_guidelines/index.md
new file mode 100644
index 00000000000..1ee22644bbc
--- /dev/null
+++ b/doc/development/deprecation_guidelines/index.md
@@ -0,0 +1,23 @@
+# Deprecation guidelines
+
+This page includes information about how and when to remove or make breaking
+changes to GitLab features.
+
+## Terminology
+
+It's important to understand the difference between **deprecation** and
+**removal**:
+
+**Deprecation** is the process of flagging/marking/announcing that a feature
+will be removed in a future version of GitLab.
+
+**Removal** is the process of actually removing a feature that was previously
+deprecated.
+
+## When can a feature be deprecated?
+
+A feature can be deprecated at any time, provided there is a viable alternative.
+
+## When can a feature be removed/changed?
+
+See our [Release and Maintenance policy](../../policy/maintenance.md).