doc: update backport section

Only maintainers can set labels on PRs, so let's clarify that point in
the doc which says something confusing at the moment.

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5e2da6e6b7a1433c7a1721ae19ccb7a371c2a7e1..8d76b9754b4feb615bd2768e06504fc4ed9f5af6 100644 (file)
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -41,9 +41,9 @@ This will prevent the engine merging your pull request.
 
 ### Backports (maintainers only)
 
-If you wish to see your work from 'master' being backported to a stable branch you can apply a label on the PR that points to the desired stable branch.
-Labels for backports are name: `backport-stable-<branch version>`, eg: `backport-stable-3.2`.
-Once the PR from master is merged, a backport PR will be created by mergify, if there is a cherry-pick conflict you must resolv it by pulling the branch.
+If you wish to see your work from 'master' being backported to a stable branch you can ping a maintainer
+so he will set the backport label on your PR. Once the PR from master is merged, a backport PR will be created by mergify,
+if there is a cherry-pick conflict you must resolv it by pulling the branch.
 
 **NEVER** push directly into a stable branch, **unless** the code from master has diverged so much that the files don't exist in the stable branch.
 If that happens, inform the maintainers of the reasons why you pushed directly into a stable branch, if the reason is invalid, maintainers will immediatly close your pull request.