Skip to content
Snippets Groups Projects
Commit 680a8c30 authored by Brian Rhea's avatar Brian Rhea :speech_balloon:
Browse files

Squash commits for dangerbot

parent 3c9803ca
No related branches found
No related tags found
1 merge request!80756Update deprecation terms
Pipeline #549958023 passed
......@@ -11,13 +11,29 @@ changes](../contributing/index.md#breaking-changes) to GitLab features.
## Terminology
It's important to understand the difference between **deprecation** and
**removal**:
**Deprecation**:
**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.
- Feature not recommended for use.
- Development restricted to Priority 1 / Severity 1 bug fixes.
- Will be removed in a future major release.
- Begins after a deprecation announcement outlining an end-of-support date.
- Ends after the end-of-support date or removal date has passed.
**Removal** is the process of actually removing a feature that was previously
deprecated.
**End of Support**:
- Feature usage strongly discouraged.
- No support or fixes provided.
- No longer tested internally.
- Will be removed in a future major release.
- Begins after an end-of-support date has passed.
- Ends after all relevant code has been removed.
**Removal**:
- Feature usage impossible.
- Happens in a major release in line with our
[semantic versioning policy](../../policy/maintenance.md).
- Begins after removal date has passed.
## When can a feature be deprecated?
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment