From f19bc8d91323a8640925256c4dacee331b05cdcc Mon Sep 17 00:00:00 2001 From: Robert Date: Tue, 2 Jun 2026 17:04:43 +0000 Subject: [PATCH] =?UTF-8?q?Add=20=F0=9F=A5=9A=20to=20README?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- security/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/security/README.md b/security/README.md index 8f6e4c45b..e9175ac8d 100644 --- a/security/README.md +++ b/security/README.md @@ -32,3 +32,5 @@ As the security issue moves from triage, to identified fix, to release planning A public disclosure date is negotiated by the etcd Product Security Committee and the bug reporter. We prefer to fully disclose the bug as soon as possible once user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. As a basic default, we expect report date to disclosure date to be on the order of 7 days. The etcd Product Security Committee holds the final say when setting a disclosure date. Hello World 2 + +🥚 \ No newline at end of file