[llvm] 17ee4ae - [docs] Update expected cadence of when Transparency reports are published (#142026)

[via llvm-commits]

Author: Cyndy Ishida
Date: 2025-05-29T13:48:35-07:00
New Revision: 17ee4aecdab466003717149ce61bd593cd211048

URL: https://github.com/llvm/llvm-project/commit/17ee4aecdab466003717149ce61bd593cd211048
DIFF: https://github.com/llvm/llvm-project/commit/17ee4aecdab466003717149ce61bd593cd211048.diff

LOG: [docs] Update expected cadence of when Transparency reports are published (#142026)

Added: 
    

Modified: 
    llvm/docs/ResponseGuide.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/ResponseGuide.rst b/llvm/docs/ResponseGuide.rst
index 55033ce7f333d..56dc5e9831994 100644
--- a/llvm/docs/ResponseGuide.rst
+++ b/llvm/docs/ResponseGuide.rst
@@ -283,9 +283,7 @@ Transparency Reports
 Lack of transparency in the outcomes of our Code of Conduct incidents leaves
 our community without an understanding of how or if the organizers worked to
 resolve incidents. The CoC committee should aim to publish transparency
-reports, if reports are received, after major events (such as the LLVM
-Developers' meetings) and on the following dates: Jan 15, April 15, July 15,
-Oct 15. 
+reports, if reports are received, at least 2 times in a calendar year.
 
 A transparency report consists of 2 parts: