Well, "Nothing specific for this version." in the upgrade notes is clearly wrong.
Upgrading effectively broke our all our builds:
First: Your change of the license model could have been communicated more clearly. We are using commercial plugins and after the update the system determined that we use one of your commercial editions and that we have too many lines for that. So storing any new analysis effectively failed. Combined with the fact that our admins tried to contact your support to at least get a temporary solution (trial), while sorting everything out, but did not get any answer up to now, this is really annoying.
Second (this already for 6.6, we upgraded from 6.5), dropping the support of a feature (issues reports) could have been more clearly communicated as well, before breaking a lot of pipelines out there. I would consider dropping of formerly working features (although deemed deprecated) being something that needs to be part of upgrade notes.
Please consider including such information clearly in the upgrade notes in the future, this might save a lot of headaches. (Was there some offical announcement about the change of the license model anywhere? I don't remember seeing anything like it on the blog).
Cheers,
Stephan