summaryrefslogtreecommitdiff
path: root/doc/administration/package_information
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2021-10-19 03:11:34 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2021-10-19 03:11:34 +0000
commitdc97e5514114912508318ada1d35666d85fd3ab7 (patch)
tree1fe49bccc30546c36876e1ae35f4ca32641254f9 /doc/administration/package_information
parent7e1b27cedb9aa52f13f3d4120dac8cdb6cfc0dda (diff)
downloadgitlab-ce-dc97e5514114912508318ada1d35666d85fd3ab7.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/package_information')
-rw-r--r--doc/administration/package_information/deprecation_policy.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/administration/package_information/deprecation_policy.md b/doc/administration/package_information/deprecation_policy.md
index 80ce72d54f5..d45c2ea3127 100644
--- a/doc/administration/package_information/deprecation_policy.md
+++ b/doc/administration/package_information/deprecation_policy.md
@@ -1,7 +1,7 @@
---
stage: Enablement
group: Distribution
-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/#designated-technical-writers
+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
---
# Deprecation policy **(FREE SELF)**
@@ -35,9 +35,11 @@ This section lists steps necessary for deprecating and removing configuration.
We can differentiate two different types of configuration:
-- Sensitive: Configuration that can cause major service outage ( Data integrity,
- installation integrity, preventing users from reaching the installation, etc.)
-- Regular: Configuration that can make a feature unavailable but still makes the installation useable ( Change in default project/group settings, miscommunication with other components and similar )
+- Sensitive: Configuration that can cause major service outage (like data integrity,
+ installation integrity, or preventing users from reaching the installation)
+- Regular: Configuration that can make a feature unavailable but still makes the
+ installation useable (like a change in default project/group settings, or
+ miscommunication with other components)
We also need to differentiate deprecation and removal procedure.