-
Notifications
You must be signed in to change notification settings - Fork 542
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1480 from camilamacedo86/add-bug-report
doc: add reporting bugs doc and small nit improvements in the README
- Loading branch information
Showing
2 changed files
with
39 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Reporting bugs | ||
|
||
If any part of the operator-lifecycle-manager project has bugs or documentation mistakes, please let us know by [opening an issue][operator-olm-issue]. We treat bugs and mistakes very seriously and believe no issue is too small. Before creating a bug report, please check that an issue reporting the same problem does not already exist. | ||
To make the bug report accurate and easy to understand, please try to create bug reports that are: | ||
|
||
- Specific. Include as much details as possible: which version, what environment, what configuration, etc. | ||
|
||
- Reproducible. Include the steps to reproduce the problem. We understand some issues might be hard to reproduce, please include the steps that might lead to the problem. | ||
|
||
- Isolated. Please try to isolate and reproduce the bug with minimum dependencies. It would significantly slow down the speed to fix a bug if too many dependencies are involved in a bug report. Debugging external systems that rely on operator-lifecycle-manager is out of scope, but we are happy to provide guidance in the right direction or help with using operator-lifecycle-manager itself. | ||
|
||
- Unique. Do not duplicate existing bug report. | ||
|
||
- Scoped. One bug per report. Do not follow up with another bug inside one report. | ||
|
||
It may be worthwhile to read [Elika Etemad’s article on filing good bug reports][filing-good-bugs] before creating a bug report. | ||
|
||
We might ask for further information to locate a bug. A duplicated bug report will be closed. | ||
|
||
[operator-olm-issue]: https://github.com/operator-framework/operator-lifecycle-manager/issues/new | ||
[filing-good-bugs]: http://fantasai.inkedblade.net/style/talks/filing-good-bugs/ |