Interestingly, it looks like the released code is closely related to the beta code... Build date and time of the released files are March 15, 2012 at 3:22 am (someone was burning the midnight oil).
I guess that says they didn't feel anything was too terribly wrong with the beta version.
I only mention this because it seems to mean that retaining the preferences, workspace, et. al., that we have set up during the testing of the CS6 beta version will still be perfectly valid.
Normally I would advise to delete preferences during the uninstall of the beta and recreate everything, but (unless one of the Adobe folks chimes in here and says otherwise) I'd say it's likely to be okay to keep them. That would be kind of nice not to have to re-setup Photoshop CS6.
I hadn't even thought about there being a problem keeping Preferences, but that sort of thing is more your field Noel. I was actually asked wheter to delete Preferences when uninstalling the beta. Workspaces etc. have all carried over OK here.
That's a fancy new splash screen btw.
Well, given that Photoshop CS6 strives to port preferences from older versions, one might think that it might have been an Adobe design goal to try not to leave the folks who tried the public out in the cold by making them go through the process of setting up CS6 twice.
I am a little surprised Adobe did not rebuild the software before release per some of the beta feedback, since some of the bugs reported seemed pretty serious (thinking, for example, of the one where under some condition it can corrupt text in a PSD file so that it's uneditable)... Clearly they place a LOT of emphasis on their system testing, and apparently no bug was considered a "show stopper".
But I imagine they're working hard to get an update out. Also they must be planning to update Camera Raw to 7.1 soon, to bring back Camera support already in 6.7.
I expect you've seen the link for 7.1 that just went up?
The daily automated build process starts at 2am :-)
We did patch the most critical known bugs, but had to freeze the code at some point.
Plus we can expect more bugs to be found once the release gets out to more users.
And yes, we try to keep preferences continuously working -- otherwise it would make even our development more difficult.
Europe, Middle East and Africa