github.com/operator-framework/operator-lifecycle-manager@v0.30.0/doc/dev/reporting_bugs.md (about)

     1  # Reporting bugs
     2  
     3  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.
     4  To make the bug report accurate and easy to understand, please try to create bug reports that are:
     5  
     6  - Specific. Include as much details as possible: which version, what environment, what configuration, etc.
     7  
     8  - 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.
     9  
    10  - 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.
    11  
    12  - Unique. Do not duplicate existing bug report.
    13  
    14  - Scoped. One bug per report. Do not follow up with another bug inside one report.
    15  
    16  It may be worthwhile to read [Elika Etemad’s article on filing good bug reports][filing-good-bugs] before creating a bug report.
    17  
    18  We might ask for further information to locate a bug. A duplicated bug report will be closed.
    19  
    20  [operator-olm-issue]: https://github.com/operator-framework/operator-lifecycle-manager/issues/new
    21  [filing-good-bugs]: http://fantasai.inkedblade.net/style/talks/filing-good-bugs/