Dear Jules & other JUCE'rs.
This is my first post in this forum, but I have been an extremely happy JUCE user for 6+ months. Please forgive me if I'm asking a question that I could have found the answer for elsewhere. Please consider this post as an attempt to understand the development process of JUCE.
I am a experienced git user and am currently using the tagged version 3.1.1 from github for my project's master branch (production code) and have a local development branch for my project, which uses the current master branch from github. This is intended to make sure I only have stable versions of JUCE in my master branch. Is this the preferred way to do it, the JUCE way? Meaning, are the tagged versions considered stable - or is everything in the master branch of JUCE stable enough to be used for production code?
It seems that there has been no tagged version since v3.1.1 from Dec 16, 2014, but a significant number of commits (330+) since then. It is difficult to make out of the individual commits on github what exactly is being worked on. Is there a webpage somewhere which lists these things, and things like breaking changes etc.? Or should you watch release notes (where should I find these), or simply read every single commit?
So to sum it up, my questions are:
- Is the master branch considered stable?
- Are releases/tags considered stable? Where to find release notes?
- Or, is it left up to ourselves to do the testing and management of breaking changes? :)
Thanks for the wonderful work done to make this library what it is. I will for sure be a paying customer in the near future.