This is an automated email from the ASF dual-hosted git repository.
DaanHoogland pushed a commit to branch staging-site
in repository https://gitbox.apache.org/repos/asf/cloudstack-www.git
The following commit(s) were added to refs/heads/staging-site by this push:
new f81be0196 Fix wording in security.md regarding issue timelines
f81be0196 is described below
commit f81be0196cde8d6f21f48ed6ca1e36479f5d4ef3
Author: dahn <[email protected]>
AuthorDate: Wed Jun 10 16:39:16 2026 +0200
Fix wording in security.md regarding issue timelines
---
src/pages/security.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/pages/security.md b/src/pages/security.md
index c55d96dad..22353bd0f 100644
--- a/src/pages/security.md
+++ b/src/pages/security.md
@@ -44,7 +44,7 @@ PMC through validation and fixing the issue. If the issue is
validated, it will still take time to fix the issue. The amount of
time depends on the availability of volunteers and number people
involved that have a stake in the issue. In later years it has turned
-out to take up to six months, from notification to public announcement
+out to take more and more time from notification to public announcement
of the vulnerability, due to parallel work on multiple issues. During
this time, the team will communicate with you as they proceed through
the response procedure, and ask that the issue not be announced before
