; Minor addition to CONTRIBUTE

* CONTRIBUTE (http): Mention that doc fixes should always go to
the release branch.

diff --git a/CONTRIBUTE b/CONTRIBUTE
index a70682f29ab63a8c21868d2532808825edf52214..a02acadc73fb2365f34acc3f173d865e835c623d 100644 (file)
--- 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