Commit c6dd0b81 authored by Nathan Friend's avatar Nathan Friend

Merge branch 'add-link-to-release-post-deprecations' into 'master'

Add links to deprecations release posts to deprecation policy

See merge request gitlab-org/gitlab!63029
parents 7783c9b7 6cdbc153
...@@ -24,8 +24,13 @@ deprecated. ...@@ -24,8 +24,13 @@ deprecated.
A feature can be deprecated at any time, provided there is a viable alternative. 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? ## 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 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). For configuration removals, see the [Omnibus deprecation policy](https://docs.gitlab.com/omnibus/package-information/deprecation_policy.html).
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment