Please email me with more questions if you'd like me to add them here. And let me know if any of these answers seem to be wrong or out-of-date!
This really depends on what I decide to add to each release, but I'll only make changes that require changes to client-code if there's a good reason for it. In general most new releases haven't affected any client-code, but where it does I'll explain what to do in the release notes. I also try to ensure that any changes break the code at compile-time, rather than causing unexpected problems later on.
Currently it runs on Windows 98ME, 2000 and XP; MacOSX 10.2 and later; Linux kernel 2.6 and later (maybe also ok under 2.4 but I've not tested this).
On Windows, you can use VC6, VC7, VCExpress or Dev-C++. On the Mac, XCode 2.0 or later. On Linux, GCC 3.3 or later. It's probably quite easy to port to other environments, but these are the ones I currently maintain support for.
The number of known bugs is always zero, because if I see or hear about a bug I fix it immediately. The number of actual bugs is of course unknown, but I think it's pretty low!
Difficult to judge how many open-source users there are, but there's a list of some of the commercial users here
I'm not actively seeking third-party code for Juce itself, as I like to keep very tight control over what goes into it. I've found that checking someone else's work for bugs, and editing it for style and consistency with the rest of the library is usually slower than just writing the same code myself!
If you're going to sell or distribute a product without also distributing your source-code, you'll need to buy a commercial licence.
Yes, you can upgrade by paying the difference between the two prices.
The licences apply to to a specific company and are non-transferable, so the company buying your product would need to have their own licence.
No, the commercial licence never expires, so you won't have to renew it if you continue using a version of Juce before V3. In fact, I've got no plans currently for a V3 - the clause in the licence is only there as a precaution in case I decide to make a major change to the library at some point in the future.
***