It is also surprising to us that Joomla 1.7 is a security upgrade to Joomla 1.6.5, and that there is no Joomla 1.6.6 security release, while Joomla 1.6 should be maintained for 1 more month, giving time to extensions to test and release Joomla 1.7-compatible stable versions, which is impossible overnight.
As you said, I wanted to update due to security reasons. The new Joomla-Update-Strategy ist still confusing for me, just because it seems to be non-synchronized with all programmers for the modules and so on.
I just feel as a kind of CMS-Guinea-Pig for testing, and I don't like the Joomla team making me feel so. You're perfectly right about a missing Joomla 1.6.6-Version as an Security update, I think it would be good to adress this to the Joomla-team.
I worked out all hints before update, esp. Backup, Backup, Backup, what helped me survive.
As a hint for all here: I used Akeeba-Backup with the additional Kickstart-Tool for Restore, which made my day. The rollback took only a few minutes. Akeeba ist absolutely great.
Just as a guess: It would be helpful if Joomlapolis could make a Newsbox on the mainpage just adressing if the actual version would be compatible, when a Joomla-Update occurs.
And to make this clear: I'm angry about Joomla for the new Update-strategy, NOT about Joomlapolis.
(same message put in general as there are 2 topics on the same subject)
By the way. In case fall back to joomla 1.6.5 is too diffucult or impossible for you.
You could enter your database webadmin and disable cb core and plugins/modules so your frontend is visible normal again. But your users can't enter the way they normally do.
So now you can put a message on that they have to wait a little while.
beat
