[llvm] [llvm][docs] Remove guidance on adding release:reviewed label (PR #164395)
Cullen Rhodes via llvm-commits
llvm-commits at lists.llvm.org
Tue Oct 21 03:49:28 PDT 2025
https://github.com/c-rhodes created https://github.com/llvm/llvm-project/pull/164395
"How To Release LLVM To The Public" [1] mentions to add the release:reviewed label once a bug has been reviewed, but looking at the label [2] it seems this hasn't been followed for quite a long time, so I propose we remove it.
[1] https://llvm.org/docs/HowToReleaseLLVM.html#triaging-bug-reports-for-releases
[2] https://github.com/llvm/llvm-project/issues?q=label%3Arelease%3Areviewed
>From 919c6166d9fe95705cdf8a96ab6089919aae0e08 Mon Sep 17 00:00:00 2001
From: Cullen Rhodes <cullen.rhodes at arm.com>
Date: Tue, 21 Oct 2025 10:37:27 +0000
Subject: [PATCH] [llvm][docs] Remove guidance on adding release:reviewed label
"How To Release LLVM To The Public" [1] mentions to add the
release:reviewed label once a bug has been reviewed, but looking at the
label [2] it seems this hasn't been followed for quite a long time, so I
propose we remove it.
[1] https://llvm.org/docs/HowToReleaseLLVM.html#triaging-bug-reports-for-releases
[2] https://github.com/llvm/llvm-project/issues?q=label%3Arelease%3Areviewed
---
llvm/docs/HowToReleaseLLVM.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/llvm/docs/HowToReleaseLLVM.rst b/llvm/docs/HowToReleaseLLVM.rst
index 171bf889256cd..c269cc4c54bcc 100644
--- a/llvm/docs/HowToReleaseLLVM.rst
+++ b/llvm/docs/HowToReleaseLLVM.rst
@@ -311,10 +311,10 @@ This section describes how to triage bug reports:
to backport. You should also review the bug yourself to ensure that it
meets the requirements for committing to the release branch.
-#. Once a bug has been reviewed, add the release:reviewed label and update the
- issue's status to "Needs Merge". Check the pull request associated with the
- issue. If all the tests pass, then the pull request can be merged. If not,
- then add a comment on the issue asking someone to take a look at the failures.
+#. Once a bug has been reviewed, update the status to "Needs Merge". Check the
+ pull request associated with the issue. If all the tests pass, then the pull
+ request can be merged. If not, then add a comment on the issue asking
+ someone to take a look at the failures.
Release Patch Rules
More information about the llvm-commits
mailing list