diff options
| author |  Abhishek Arya <inferno@chromium.org> | 2017-01-05 13:41:57 -0800 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2017-01-05 13:41:57 -0800 |
| commit | c878342c537f3bd06d88c67bae593db76abca94e (patch) | |
| tree | 06b8db3e6f01fee78893e5ca933399870d9d7868 /README.md | |
| parent | 23b72b4130f7d876d0b38252db3f5a27197318b7 (diff) | |
Update README.md
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -49,7 +49,8 @@ and [integrates](docs/ideal_integration.md) them with the project's build and te ([example](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9)). ([Why different tracker?](docs/faq.md#why-do-you-use-a-different-issue-tracker-for-reporting-bugs-in-oss-projects)). Project owners are CC-ed to the bug report. -- The bug is fixed upstream. +- 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* ([guidelines](#bug-disclosure-guidelines)). |