From d1aa552d11484ab15944a1f3c15f607dda811d8d Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Thu, 25 Nov 2021 10:43:35 +0200 Subject: [PATCH] ; * CONTRIBUTE: No cleanups on release branches, even in docs. --- CONTRIBUTE | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTE b/CONTRIBUTE index 8295a8e6ad4..5740004637b 100644 --- a/CONTRIBUTE +++ b/CONTRIBUTE @@ -342,7 +342,9 @@ Documentation fixes (in doc strings, in manuals, in NEWS, and in comments) should always go to the release branch, if the documentation to be fixed exists and is relevant to the release-branch codebase. Doc fixes are always considered "safe" -- even when a release branch -is in feature freeze, it can still receive doc fixes. +is in feature freeze, it can still receive doc fixes. However, this +rule is limited to fixing real problems in the documentation; cleanups +and stylistic changes are excluded. When you know that the change will be difficult to merge to the master (e.g., because the code on master has changed a lot), you can -- 2.39.2