I’ve used the tip on and off for about a year now and I’ve had a generally good experience with it.
Once there was a new, small problem that Jules fixed almost immediately. But several times I’ve had to stop development and change things because some part of Juce changed and I needed to change my code. The worst was I think when the leak detector came in - I had several leaks of Juce things from non-obvious causes and had to stop and spend some time tracking it down but this overall improved my code quality (it was only singletons being leaked but it’s really good to make sure you have kept track of every item).
I was away for months and at some point there was a serious change to the model of String. That was also somewhat eventful, since I convert quite a bit back and forth from String to std::string due to my other libraries but this convinced me to bring all that out into a single routine that really makes it much better for me anyway.
I have a reasonably large app that touches on lots of parts of Juce so I might be “impacted” (as they say around here) more than most by changes. All of these were changes for the better, there’s no question.
So yes, if you stay on the tip you can expect that occasionally when you update you’ll have to make changes to your code to get it to compile, and very rarely, there will be some small bug that Jules will fix expeditiously given enough information to isolate it (and since you have all the code to look at, you can just tell him what’s wrong :-D)/