After popular request, JUCE has now enabled the issue tracker in github. You can now submit bugs via this issue tracker and we will look (and try to fix) every issue.
A good issue should have detailed steps on how to reproduce the bug, preferably with already existing JUCE code such as the demo plugin or the demo code. It should include what you expect the outcome to be.
If it’s a crash a stack trace is absolutely essential. Also don’t forget to mention the OS, the architecture (32-bit or 64-bit), the plugin format (VST2, VST3, AU, AAX, RTAS) and in which DAW you observe the bug - if applicable.
Also always make sure you have pulled the latest commits from the JUCE repo and re-compiled the Projucer before you submit your bug. If it’s a major bug, which must be hot-fixed immediately then we will also accept bug reports for tagged release versions.
We’d like to stress that this does not mean we will be looking at the forum any less. The forum is a vital and fun part of JUCE’s community and we’d rather have users post problems and possible bugs too often than too little. If your problem turns out to be a bug then you can still file it with more detailed information as an issue.