That was Adobe's fantasies and no, it was purely a bug of their own creation for both Photoshop and LR (the former is fixed too FWIW). In fact, Apple's Preview and ColorSync utility printed correctly and much like my 'control', Photoshop CS6. Simply ridiculous to think this was an Apple bug or a print driver bug.
From what I understand reading various posts, the reality is a bit more complicated, but the responsibility isn't. I understand based on what I read in the Adobe Forum that the problem started with Apple deleting or amending some APIs that affected LR and PS for Mac OSX. I also understand that when Apple intends to make these changes, they provide them to developers about six months before publication allowing those developers to update their applications as necessary. If this is all correct, then one could credibly surmise that Adobe did not implement the necessary modifications to LR and PS print pipelines correctly, and also failed to adequately quality check their implementation. As I've mentioned elsewhere, in the final analysis, unless each developer remains responsible for their own applications, there is chaos; and if implementing that responsibility requires collaboration with the OS provider so be it. Now, even if Apple had not provided enough time or information to assure a faultless updating at Adobe, one could also credibly argue that with proper QA, the issue would have been detected before release and the two companies would talk enough to fix whatever. Anyhow, all this is now history.
Not to say history should be dismissed - we can do so as consumers provided the product is now OK, which I think it is; however, for the company it is a different story. There is something in the corporate environment (generally, not specific to any one industry) called "Lessons of Experience". I've lived through years of this, so I have a pretty clear view of what it involves. The basic philosophy is that when screw-ups occur, which for all kinds of reasons they can, it's important to diagnose exactly what happened, how, why, and what could have been done, with the benefit of hindsight, to apprehend them. The more thorough and probing the analysis, the more useful the results. The findings go into a report which becomes part of the corporation's "institutional memory". Then the next time a similar project or set of actions comes up, it is the responsibility of the quality checkers to make sure the project team has reviewed the relevant "Lessons of Experience" and taken the indicated measures to prevent a re-occurrence. One fervently hopes that Adobe has or will have such internal "Lessons of Experience" procedures in place to minimize the risk of future issues interfering with the smooth transition of the applications from one version to the next.
