2020-10-30 18:08:56 +00:00
---
stage: none
group: unassigned
2020-11-26 06:09:20 +00:00
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-10-30 18:08:56 +00:00
---
2020-07-27 09:09:42 +00:00
# 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
2020-12-16 15:10:18 +00:00
is scheduled for removal in a future version of GitLab.
2020-07-27 09:09:42 +00:00
**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.
2021-06-02 21:10:00 +00:00
Deprecations should be announced via [release posts ](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations ).
2020-07-27 09:09:42 +00:00
## When can a feature be removed/changed?
2021-06-02 21:10:00 +00:00
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 ).
2021-06-28 15:08:03 +00:00
For API removals, see the [GraphQL ](../../api/graphql/index.md#deprecation-and-removal-process ) and [GitLab API ](../../api/index.md#compatibility-guidelines ) guidelines.
2021-04-15 18:09:01 +00:00
For configuration removals, see the [Omnibus deprecation policy ](https://docs.gitlab.com/omnibus/package-information/deprecation_policy.html ).
For versioning and upgrade details, see our [Release and Maintenance policy ](../../policy/maintenance.md ).