diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-27 12:09:42 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-27 12:09:42 +0300 |
commit | 43b35a88ca54379d8df4dad84b5a84f9eecae3f2 (patch) | |
tree | c05f56f7663a268f437c738558168c3915cce143 /doc/development/deprecation_guidelines | |
parent | 90cd3934092f58d570ab8b5014189d257505bfc6 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/deprecation_guidelines')
-rw-r--r-- | doc/development/deprecation_guidelines/index.md | 23 |
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). |