[llvm] [llvm][docs] Tweak backporting instructions a bit (PR #126519)

[Nico Weber via llvm-commits]

https://github.com/nico created https://github.com/llvm/llvm-project/pull/126519

* Drop ".Z" in milestone name since we've been doing X.Y releases instead of X.Y.Z releases since LLVM 18

* Add "LLVM" prefix since that's what release milestones are named

* Use a numbered list to make it clearer that there are two steps needed, and add some more details to the first step

>From 2172fc40e15a07f99a579485d2c2d735e7767063 Mon Sep 17 00:00:00 2001
From: Nico Weber <thakis at chromium.org>
Date: Mon, 10 Feb 2025 09:09:37 -0500
Subject: [PATCH] [llvm][docs] Tweak backporting instructions a bit

* Drop ".Z" in milestone name since we've been doing X.Y releases
  instead of X.Y.Z releases since LLVM 18

* Add "LLVM" prefix since that's what release milestones are named

* Use a numbered list to make it clearer that there are two steps
  needed, and add some more details to the first step
---
 llvm/docs/GitHub.rst | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/llvm/docs/GitHub.rst b/llvm/docs/GitHub.rst
index 892b8abcc2d4e25..b5b75db91e1c436 100644
--- a/llvm/docs/GitHub.rst
+++ b/llvm/docs/GitHub.rst
@@ -438,9 +438,13 @@ Releases
 Backporting Fixes to the Release Branches
 -----------------------------------------
 You can use special comments on issues or pull requests to make backport
-requests for the release branches.  This is done by making a comment containing
-the following command on any issue or pull request that has been added to one
-of the "X.Y.Z Release" milestones.
+requests for the release branches.  To do this, after your pull reuest has been
+merged:
+
+1. Edit "Milestone" at the right side of the isssue or pull request
+   to say "LLVM X.Y Release"
+
+2. Add a comment to it in the following format:
 
 ::