aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorOliver Chang <oliverchang@users.noreply.github.com>2017-03-03 14:21:37 -0800
committerGitHub <noreply@github.com>2017-03-03 14:21:37 -0800
commitc2f88ee60f8a298762fb5c07429f0d2ec194fecd (patch)
tree3016fd37f4ef4ef862d9cc627b2bb0ab8ada1ffe /README.md
parent062995726ec7c5307bc94d59912660d7a9066428 (diff)
downloadoss-fuzz-c2f88ee60f8a298762fb5c07429f0d2ec194fecd.tar.gz
Update README.md
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 613f47ee2..19f261299 100644
--- a/README.md
+++ b/README.md
@@ -55,7 +55,7 @@ and [integrates](docs/ideal_integration.md) them with the project's build and te
- The project developer fixes the bug upstream and credits OSS-Fuzz for the discovery (commit message should contain
the string **'Credit to OSS-Fuzz'**).
- [ClusterFuzz](docs/clusterfuzz.md) automatically verifies the fix, adds a comment and closes the issue ([example](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=53#c3)).
-- 7 days after the fix is verified or 90 days after reporting, the issue becomes *public*
+- 30 days after the fix is verified or 90 days after reporting (whichever is earlier), the issue becomes *public*
([guidelines](#bug-disclosure-guidelines)).
<!-- NOTE: this anchor is referenced by oss-fuzz blog post -->