JUCE 9: No pricing or EULA changes

News and Announcements
1

This post is taken from the JUCE email newsletter.

To get these delivered to your email inbox, sign up here: Newsletter - JUCE

We’re currently preparing JUCE 9 for release and we have some news to share about JUCE 9’s pricing and licensing.

No pricing changes

JUCE 9 will retain the same divisions between licensing tiers, and the price for each tier will remain the same. This means that whichever tier you are currently using for JUCE 8 will map directly onto the same tier for JUCE 9 with no changes to how you are billed.

No EULA Changes

The JUCE 9 End User License Agreement is also remaining unchanged from the last iteration of JUCE 8. If you have been licensing JUCE 8 then the transition to JUCE 9 should be completely smooth, with no additional restrictions on how JUCE can be used.

You can find the new EULA here: The JUCE 9 End User Licence Agreement - JUCE

Subscription Licensing

All JUCE 8 subscriptions will be upgraded to JUCE 9 subscriptions when JUCE 9 is released. Given that the pricing and EULA are remaining the same it seems unlikely that this will cause anyone to consider cancelling their subscription, but if you are a subscriber and you wish to remain on a JUCE 8 licence you should purchase a JUCE 8 perpetual licence in the next 30 days and cancel your JUCE 8 subscription.

As with previous versions of JUCE, a JUCE 9 licence will allow you to continue using JUCE 8.

Timeline

We’re still testing the initial release of JUCE 9, which can be found on the juce9 branch of our public repo. We would love to get your feedback on the new features, and expose the changes to as many different operating systems and compilers as possible. If you are able to try out the new branch and report back, it would be much appreciated - this will make the release more stable for everyone.

You can find the JUCE Forum thread about the JUCE 9 preview branch here: https://forum.juce.com/t/the-juce-9-preview-branch-is-available-now

Whilst we’re nearing a state when we can release, this will be at least 30 days from now, and a bit longer if we uncover any problems that take significant time to fix. If you want to be kept up to date with progress please follow the discussion on the forum.

Best wishes,

The JUCE Team

6 Likes
3

There might be another post on this somewhere, but what will backwards compatibility look like for JUCE 9 - are we going to need to revisit code to make changes?

Thank you,
Jeff

4

We’re aiming to keep the number of breaking changes low (if you are updating from the latest JUCE 8 release) but there may be some alterations in your code required.

You can find out very precisely how you would be affected by giving the new branch a try, but otherwise we have changes documented in the BREAKING_CHANGES.md file: