Rory, I think the fact is that by the time they are ready to issue a new release, it isn't to solve previous operating problems - those are dealt with long beforehand; it is to introduce support for new cameras, new security concerns and new features; more often than not those new features are very worthwhile. For example, the new Transform Panel is something I have been using every day and it is excellent. They also do stuff to improve efficiency under the hood and that is also welcome. The main problem is the self-evident short-circuiting of QC/QR, which is unfortunate, because as an application grows in complexity and sophistication, and the needs and computing environments of users expand, one has to expect scope for glitches. There was a time when Adobe had a very extensive external testing apparatus in place, especially in the very early days of the application. I think they need to seriously consider re-introducing this approach, which will be of interest to the early adopters who either don't mind or even enjoy being beta testers with its attendant risks; this would be in the interest of both the company and the rest of the clientele who just want things that work properly when the commercial release happens. Of course it uses supervisory/management resources and perhaps they are reluctant to spend that money.