[llvm] 308d286 - [llvm][docs] Tweak backporting instructions a bit (#126519)

[via llvm-commits]

Author: Nico Weber
Date: 2025-02-10T10:58:16-05:00
New Revision: 308d28667c14e7c14d8688cd19201308e07c8721

URL: https://github.com/llvm/llvm-project/commit/308d28667c14e7c14d8688cd19201308e07c8721
DIFF: https://github.com/llvm/llvm-project/commit/308d28667c14e7c14d8688cd19201308e07c8721.diff

LOG: [llvm][docs] Tweak backporting instructions a bit (#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

Added: 
    

Modified: 
    llvm/docs/GitHub.rst

Removed: 
    


################################################################################
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:
 
 ::