From ec6e4b9d1e5a215d9dfe1026730dbb23f1935615 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Tue, 4 Oct 2016 08:59:37 +0300 Subject: [PATCH] ; Minor addition to CONTRIBUTE * CONTRIBUTE (http): Mention that doc fixes should always go to the release branch. --- CONTRIBUTE | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CONTRIBUTE b/CONTRIBUTE index a70682f29ab..a02acadc73f 100644 --- a/CONTRIBUTE +++ b/CONTRIBUTE @@ -189,6 +189,10 @@ If you are fixing a bug that exists in the current release, be sure to commit it to the release branch; it will be merged to the master branch later by the gitmerge function. +Documentation fixes (in doc strings, in manuals, 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. + However, if 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 apply the change to both master and branch yourself. It could also -- 2.39.5