summaryrefslogtreecommitdiff
path: root/docs/internals/release-process.txt
diff options
context:
space:
mode:
authorMariusz Felisiak <felisiak.mariusz@gmail.com>2022-03-22 11:13:36 +0100
committerGitHub <noreply@github.com>2022-03-22 11:13:36 +0100
commit653daaa60cf4de7071136541169285ed3d71974d (patch)
tree0c110182a513cceb4ca66bd1e2260cbd685ad32f /docs/internals/release-process.txt
parent7325d291524827806feed271a077ea23e2b1b21f (diff)
Refs #31676 -- Used term "merger" instead of "committer" in docs.
Follow up to caa2dd08c4722c8702588f5dfe1fa4c506aa66fc. Co-authored-by: Carlton Gibson <carlton.gibson@noumenal.es>
Diffstat (limited to 'docs/internals/release-process.txt')
-rw-r--r--docs/internals/release-process.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/internals/release-process.txt b/docs/internals/release-process.txt
index 7e899026dc..a845faf330 100644
--- a/docs/internals/release-process.txt
+++ b/docs/internals/release-process.txt
@@ -226,9 +226,9 @@ The release candidate marks the string freeze, and it happens at least two
weeks before the final release. After this point, new translatable strings
must not be added.
-During this phase, committers will be more and more conservative with
-backports, to avoid introducing regressions. After the release candidate, only
-release blockers and documentation fixes should be backported.
+During this phase, mergers will be more and more conservative with backports,
+to avoid introducing regressions. After the release candidate, only release
+blockers and documentation fixes should be backported.
In parallel to this phase, ``main`` can receive new features, to be released
in the ``A.B+1`` cycle.