I've been a DNN user since 3.X (can't remember the exact version) and have watched it grow. I'd consider myself a "fan" of DNN. Since version 4.7 I've even gone so far as not backing up my database and website when doing an upgrade. I've upgraded 3.X installs to 4.X installs with little problems. I've moved websites from one server to another, to using SQL server 2000 to 2005, 2005 express and 2008 with little to no problems.

In my opinion, after upgrading and installing DNN 5.0 and reading the issues on this forum, I think DNN 5.0 should be pulled until further testing can be done. The one thing I've liked about DNN versus other open source projects based on open source technologies is that DNN seemed mature in comparison. At this point with DNN 5.0 I'm not sure if this is the case. I'd hate to see DNN fall to the level as other open source projects in this regard.

I think Walter is right. I must say I am worried if this is the new strategy from DotNetNuke Corp.

Do not test opensource version - let the comunity understand its the Professional version that should bee used!!

I hope not..With this release the value of the company DotNetNuke halved. I dont blame any coders I blame the management. Ok some mistakes can bee done thats natural. But not to react on them in a proper way is foolhardy. An examle why not change the text on the download page to try to inform users that upgrade is not working for the moment. (it now tells "DotNetNuke 5.x is available as a general public release which means it can reliably be used in a production environment".) Furthermore in codplex some releasnotes could bee added to inform users there.

Ok its hollydays and I understand that the managemnt was trying to give the comunity a gift. Obviously no one of the management team have the guds or time to realise and act upon the mistake to release 5.0.0 whithout proper testing.

In any case I hope its not a new strategy

Jan

I don't fault DNN corp... actually thinking about it, I'll have to take some fault as part of the community that uses DNN. I'll be honest and say I really didn't bother much with the release candidates of DNN 5.0 and by doing so didn't give it the proper testing and thus the following response to the community with the results.

In this way I'd go so far as to say that the success of DNN to this point has actually been part of the problem... I (as well I assume others) have reached the point where I l look at DNN as a finished product instead of what it is... a work in progress.

This being said, I will try to do a better job with giving back to the community by testing the RC's and giving back input. I think we'd all benefit from more people doing that instead of just "taking" and then complaining if things don't "live up" to what we're expecting.