From 60b4fa71a8ce1abc43b6f6bba3c3aa1f69b15092 Mon Sep 17 00:00:00 2001 From: narimiran Date: Wed, 12 May 2021 13:57:43 +0200 Subject: [PATCH] [ci skip] correctly explain how to use `[backport]` tags --- doc/contributing.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/contributing.rst b/doc/contributing.rst index abc81dae6c..5a31d85bde 100644 --- a/doc/contributing.rst +++ b/doc/contributing.rst @@ -453,9 +453,9 @@ General commit rules 1. Important, critical bugfixes that have a tiny chance of breaking somebody's code should be backported to the latest stable release branch (currently 1.4.x) and maybe also all the way back to the 1.0.x branch. - The commit message should contain the tag ``[backport]`` for "backport to all - stable releases" and the tag ``[backport:$VERSION]`` for backporting to the - given $VERSION. + The commit message should contain the tag ``[backport]`` for "backport to the latest + stable release" and the tag ``[backport:$VERSION]`` for backporting back to the + given $VERSION (and all newer releases). 2. If you introduce changes which affect backward compatibility, make breaking changes, or have PR which is tagged as ``[feature]``,