Right, successfully updated using the 3.2.2 to 3.2.9 auto update package. All went swimmingly though I forgot to rename install afterwards, so a wobbly was thrown when I first visited the root folder. Soon corrected, however, the new installation reports that it is 3.3.0. I'll recheck the source .zip I used but I'm sure I used the correct 3.2.2 to 3.2.9 one.
All working OK including standard extensions. Core code needs a couple of patches from the change log I have though. A previous query suggested to avoid 3.3.0 in case extensions are incompatible. I will have to do more testing yet. When I have I will report on those that are not giving issues.
My only problem now is a custom extension for which support may no longer be available and I can't easily run from this BETA instance (accesses an external database). That will need to be the subject of another query in the suitable arena though.
'And what is good, Phaedrus, And what is not good—Need we ask anyone to tell us these things?'