Bug tracking process

1. Find-out as much as possible about the bug. Please check github issues if the bug is already known. Look for logs, error messages etc. Report using following URL's and include as much as possible background on the bug:

• PowerMatcher bug report
• FPAI-core bug report
• FPAI-apps bug report
• Flexiblepower-base bug report
• Flexiblepower-build-tools bug report
• FPAI-examples bug report
• Bundle-hub bug report

3. The maintainer makes sure that somebody will look at the bug, check for duplicates and thanks the contributor for sending in the bug. If the bug is an duplicate, the issue will be closed.
4. A developer will try to reproduce the bug and will look for the root-cause. The developer adds the findings to the issue. If the developer can not reproduce the bug, the developer will contact the user for more information or/and login into the users system (if possible for the user/developer). If it's impossible to re-produce the bug. The issue will be closed.
5. The developer will write a patch and tests the fix.
6. Once the patch is accepted (see Code review/test process), it will be shipped with the next release.
7. The maintainer will close the issue.