Yes. I have 9.01.01 installed on my primary site.
I did notice major changes to the user-interface from 6-9. Not all the changes were adding much to the user-experience. And Rule#1 of user-experience is that why change major things to the user-interface if it doesn't enhance the user-experience? That is the question that aggravated me for more than a decade about DNN and is sometimes ignored by some version releases of DNN. In some releases (ver 7) I could see a real emphasis on UX, but in 8 and 9 I saw a lack of it. Why is that? Curious...
I would advise DNN community to reach out to UX professionals such as myself with a background in Information Architecture on your release to a version 10.x product. By just looking first-hand at the DNN evolution of which I joined up in 2006, its not always enhancing much when your team updates the menus along with the UI and major things we users have grown accustomed to are now completed changed with a nonsensical placement and we must relearn where things are again and again.
Case in point. You have site settings, and the UI just lumps "Security, SEO, Import/Export, Site Settings, etc." all together in the menu of 9.x.
If I were an information architect and finished such a design? I'd never get another job if another IA looked at that taxonomy and navigation schema.
You should have a hierarchy that makes sense. Please someone on the team just put together a spreadsheet with a valid hierarchy.
Example of a fixing a few out of order menu items in the taxonomy:
Top level > SETTINGS
2nd LEVEL > SITE, SECURITY, SERVERS
3rd LEVEL for SITE > SEO, THEMES
4th LEVEL for SITE/THEMES > PAGE, CONTAINER, IMPORT TEMPLATE, IMPORT EXTENSION (LINK TO EXTENSION MANAGER)
Without basic Information Architecture and a real emphasis on user-experience *UX*, you'll just be removing, adding, changing, moving stuff around that continues to frustrate the community rather than to help new users learn how to use your platform. In this day in age the DNN developers cannot get away with just doing things that old way without losing members who move to the wordpress world. I'd suggest your team invest some time in this in the future releases. It can only help. Because each version I still keep seeing ill-advised taxonomy, layouts, etc. because it made sense to whatever developer put it there, but only makes sense to them - not us community users.
Please, again, if it doesn't improve the user-experience? Don't change it. It just makes for a more frustrating user-experience. Please don't break this rule in future updates.