Nathan Skrzypczak | 9ad39c0 | 2021-08-19 11:38:06 +0200 | [diff] [blame] | 1 | .. _reportingissues: |
| 2 | |
| 3 | Reporting Bugs |
| 4 | ============== |
| 5 | |
| 6 | Although every situation is different, this section describes how to |
| 7 | collect data which will help make efficient use of everyone's time |
| 8 | when dealing with vpp bugs. |
| 9 | |
Nathan Skrzypczak | 5f07b6b | 2021-11-04 10:06:51 +0100 | [diff] [blame] | 10 | FD.io's Jira server can be found at `jira.fd.io <https://jira.fd.io>`_ |
| 11 | |
Nathan Skrzypczak | 9ad39c0 | 2021-08-19 11:38:06 +0200 | [diff] [blame] | 12 | Before you press the Jira button to create a bug report - or email |
| 13 | vpp-dev@lists.fd.io - please ask yourself whether there's enough |
| 14 | information for someone else to understand and to reproduce the issue |
| 15 | given a reasonable amount of effort. **Unicast emails to maintainers, |
| 16 | committers, and the project PTL are strongly discouraged.** |
| 17 | |
| 18 | A good strategy for clear-cut bugs: file a detailed Jira ticket, and |
| 19 | then send a short description of the issue to vpp-dev@lists.fd.io, |
| 20 | perhaps from the Jira ticket description. It's fine to send email to |
| 21 | vpp-dev@lists.fd.io to ask a few questions **before** filing Jira tickets. |
| 22 | |
| 23 | .. toctree:: |
| 24 | |
| 25 | reportingissues |