It seems to me that the way DNN 5.0 was released was extremely unprofessional--especially considering that there is even now a PAID version and new PAID MODEL for the entire platform. When DNN 5.0 was first released "to production" there were a whole slew of errors--especially surrounding upgrading from earlier versions including the immediate previous version. After reports came in regarding problems, the 'standard line' was this will all be fixed in the 5.0.1 version.

When this version was released it came with the caveat "DotNetNuke 5.x is the "next generation" development branch of the DotNetNuke web application framework. DotNetNuke 5.x is available as a general public release; however it has not reached a level of maturity which would make it appropriate for production environments. As a result, it is recommended for internal usage and development environments."

WTF? I can understand this sort of thing happening when it is all Open Source and FREE, but having this happen right after the company announces they will now be charging for DNN in the "Professional" veresion is, well, just not very professional.

The product was released prematurely with NO WARNINGS regarding the issues; caused many in the community problems; and then the next version comes out with the warning that it shouldn't be used in production. The entire release should have been pulled or at leased downgraded to a Release Candidate, and appologies given to those who installed it prematurely.

If this is the way they intend to operate their "PAID MODEL"; I wouldn't want to be a stockholder. This upgrade to 5.0 has caused me to start thinking about testing Joomla!! :(

JK

I wanted to make a correction to my previous posts. I see now that there is a warning on the site. Still weak, but at least it is there. It never should have been released to production in the first place.

JK

My concern is I am going to be left in DNN 4.9.2 whilst 5.x keeps progressing further away.

There are so many areas and various portals in my DNN instance, though smaller than some I am sure... but I just don't know how I will be able to eventually test all of these things in an upgrade - the odd module on a page amongst thousands which mightn't be compatible so goes unnoticed for a while before realising it and a roll-back is too late.

Or even the mess it could make with things like localisation... though I've been breaking away from multi-locale websites and just creating a Portal for each since DNN is kinda rubbish here, and also many 3rd party modules don't cope too well either.