Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/deprecation_guidelines/index.md')
-rw-r--r--doc/development/deprecation_guidelines/index.md51
1 files changed, 49 insertions, 2 deletions
diff --git a/doc/development/deprecation_guidelines/index.md b/doc/development/deprecation_guidelines/index.md
index 08e29e373f6..cafc40ccc68 100644
--- a/doc/development/deprecation_guidelines/index.md
+++ b/doc/development/deprecation_guidelines/index.md
@@ -21,8 +21,6 @@ deprecated.
## When can a feature be deprecated?
-A feature can be deprecated at any time, provided there is a viable alternative.
-
Deprecations should be announced on the [Deprecated feature removal schedule](../../update/deprecations.md).
For steps to create a deprecation entry, see [Deprecations](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations).
@@ -37,3 +35,52 @@ For API removals, see the [GraphQL](../../api/graphql/index.md#deprecation-and-r
For configuration removals, see the [Omnibus deprecation policy](../../administration/package_information/deprecation_policy.md).
For versioning and upgrade details, see our [Release and Maintenance policy](../../policy/maintenance.md).
+
+## Update the deprecations and removals documentation
+
+The [deprecations](../../update/deprecations.md) and [removals](../../update/removals.md)
+documentation is generated from the YAML files located in
+[`gitlab/data/`](https://gitlab.com/gitlab-org/gitlab/-/tree/master/data).
+
+To update the deprecations and removals pages when an entry is added,
+edited, or removed:
+
+1. From the command line, navigate to your local clone of the [`gitlab-org/gitlab`](https://gitlab.com/gitlab-org/gitlab) project.
+1. Create, edit, or remove the YAML file under [deprecations](https://gitlab.com/gitlab-org/gitlab/-/tree/master/data/deprecations)
+ or [removals](https://gitlab.com/gitlab-org/gitlab/-/tree/master/data/removals).
+1. Compile the deprecation or removals documentation with the appropriate command:
+
+ - For deprecations:
+
+ ```shell
+ bin/rake gitlab:docs:compile_deprecations
+ ```
+
+ - For removals:
+
+ ```shell
+ bin/rake gitlab:docs:compile_removals
+ ```
+
+1. If needed, you can verify the docs are up to date with:
+
+ - For deprecations:
+
+ ```shell
+ bin/rake gitlab:docs:check_deprecations
+ ```
+
+ - For removals:
+
+ ```shell
+ bin/rake gitlab:docs:check_removals
+ ```
+
+1. Commit the updated documentation and push the changes.
+1. Create a merge request using the [Deprecations](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/merge_request_templates/Deprecations.md)
+ or [Removals](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/merge_request_templates/Removals.md) templates.
+
+Related Handbook pages:
+
+- <https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-removals-and-breaking-changes>
+- <https://about.gitlab.com/handbook/marketing/blog/release-posts/#update-the-deprecations-and-removals-docs>