Michael,
sorry, I didn't want to be rude - obviously I was mixing you up with another community member, I answered before with my past ~5k posts, I apologize - obviously I amgetting old...

There are 3 main in-depth changes, which caused 18 months of development:

• Permissions on Module Definitions and Admin module permissions
  Admin modules can be treated like any other module and you may grant "publish" permission to any role/user, i.e. include this module in the list of available modules in control panel. Unfortunately, admin modules haven't been enhanced yet to act appropriately, e.g. granting admin permission to dedicated roles only etc.
• Deny permissions
  Page, Folder and Module permissions in DNN 5 allow not only to grant but also to deny permissions, e.g. grant edit to all users but a certain role. There is still some finetuning going on, but in general this feature is implemented as expected
• New extension installer
  In DNN 5 Modules, Skins, Containers, Skin Objects, Providers, and Language Packs are called Extensions, being installed and manages using the same package format. This works very well for Modules and Skin Objects, Skins are now managable by Host users only, whie Language Packs are still struggling with missing features.

There are other changes "under the hood" and in modules, e.g. workflow in HTML (previously Text/HTML, renamed to get more attractive to newbees), which previously required usage of 3rd party modules.

Commercial versions with assurance contracts (PE, EE, EEP) do include additional features.

No problem at all, I guess I just didn't search for the correct threads that have already been posted. I do thank you for the information it was exactly what I was looking for. It seems to me that offering DNN version 5 to my clients isn't a "bad" thing. I have just been waiting and waiting to see how it all played out before moving down that road.

Thank you again for your post, your opinion is valued!