Carol,

Your frustration is understandable, but that frustration will only get worse for you if you don't accept the fact that Adobe is never, ever going to give you a more detailed answer than what Chris has offered.  To his credit, he has more intestinal fortitude than most Adobe staff in owning up to shortcomings in their software.

If I were among those giving legal advice to Adobe, I would urge them never to acknowledge a bug, much less to characterize it as critical or a priority of lesser or greater magnitude than any other.  Think about it for a minute or two.

On the other hand, I never buy any software without trying it first and making sure I can live with any limitation it might have.

Not trying to defend Adobe bean counters or apologize for them, just recognizing the fact that Adobe is a mammoth, unresponsive bureaucracy that is coldly nonchalant in its attention to customers. 

I'm sorry about that, Carol.

We can only hope that every moment of the time waiting is well spent ensuring the software changes don't break anything new.

-Noel

To me it's not a matter of how comparatively buggy a release of Photoshop is, it's how nasty the bugs are. Bugs that corrupt files are the worst by far, and CS6's text layer corruption can cost many hours of productive time to recover from, not to mention possible missed deadlines. What's more, I'm on Creative Cloud and Adobe has made airy promises of features (and presumably fixes) for subscribers inbetween general update releases. Adobe has indeed released some minor updates, and notably a "fix" for Creative Cloud's Adobe Application Manager that traded one recurring error message related to Acrobat X Pro authorization for outright crashes without any error messages. So far, I've only seen the downside of Creative Cloud in the all-to-frequent authorization login messages I get from applications and the massive pain that Acrobat X Pro's authorization bugs have proved to be.