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/policy/maintenance.md')
-rw-r--r--doc/policy/maintenance.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/policy/maintenance.md b/doc/policy/maintenance.md
index 95bc176e70a..217618c1771 100644
--- a/doc/policy/maintenance.md
+++ b/doc/policy/maintenance.md
@@ -103,12 +103,12 @@ have to adhere to various internal requirements (for example, org. compliance, v
1. Requirements consisting of extensive testing for not only stable GitLab release, but every patch version.
In cases where a strategic user has a requirement to test a feature before it is
-officially released, we can offer to create a Release Candidate (RC) version that will
-include the specific feature. This should be needed only in extreme cases and can be requested for
+officially released, we can offer to create a Release Candidate (RC) version that
+includes the specific feature. This should be needed only in extreme cases and can be requested for
consideration by raising an issue in the [release/tasks](https://gitlab.com/gitlab-org/release/tasks/-/issues/new?issuable_template=Backporting-request) issue tracker.
-It is important to note that the Release Candidate will also contain other features and changes as
+It is important to note that the Release Candidate contains other features and changes as
it is not possible to easily isolate a specific feature (similar reasons as noted above). The
-Release Candidate will be no different than any code that is deployed to GitLab.com or is publicly
+Release Candidate is no different than any code that is deployed to GitLab.com or is publicly
accessible.
### Backporting to older releases