I think everyone appreciate JUCE being open-source and transparent framework.
Announcing juce7 ahead of release and being able to access it is great.
I just have 2 scenarios I’m trying to figure out:
bugfixes: I see many “small” bugfixes being addressed fast by the JUCE team but only being pushed to juce7, so is from now on, any bugfix will only be available by upcoming release? (I’m not talking about major reactors or rewrites)
juce7 use, so basically now except GPL it’s impossible to use juce7 technical preview.
Commercial use: as far as I know, commercial licenses aren’t available.
non-gpl use: I have a free open-source app/plug-in I’m building on all platforms. I use “dual-license” to comply with vst2, aax, iOS where it’s not GPL compliant. Is there a way using early juce7 in non-gpl scenarios?
All bug fixes that are important but straightforward should be on both the juce7 and develop branches. A bug fix that has a higher risk of needing subsequent development effort might only be present on the juce7 branch.
The JUCE 7 branch is currently GPLv3-only. This allows everyone to test out the functionality in-house, or between subsidiary companies (if the owner of the licence is the parent company).
However, we anticipate publishing the JUCE 7 EULA shortly, at which point we will be able to offer early-access JUCE 7 licences on demand for people wishing to release software using JUCE 7 before the official release.
