Joe, of cource I am refering to the offical release 5.0.0.

Release notes. I tryed to tell you please act! Tell in a proper way that upgrades to 5.0.0 is not recomended. Do it on the download page do it at codeplex.

If it was packaging problems or whatever you have to take proper action. You cant blame the community for the release process. I am as sorry as I hope you are for releasing this nice piece of software whiout any proper testing. If I had known that RC2 was the last candidate I have reported more errors but I was convinced there should bee a RC3.

So please act as a manager.

Jan

I am not blaming anyone for the process.  I am saying that you are not correct when you say that no testing has occurred.  The whole point of RCs is that we think we are close to releasing the software.  If the problems getting reported are relatively minor or where the fixes pose little risk (ie you may have a showstopper that has a trivial fix), then there is no reason to continue the RC process.  We fix those issues and release the software.  That is what we did in this case.

When I look back at our major releases - 2.0, 3.0, 4.0 - I don't see this release having any more significant issues than those that occured in those previous releases.  I am not ashamed or sorry for the release.  For many people, DNN 5 is appropriate for use in production.  As usual, I would never recommend pushing a release into production without doing the necessary backups and internal testing.

I logged 151 issues for Cambrian in total (in addition I tried to validate other peoples issues), Jan logged 4. I'm a community member as well, nobody is paying me and I'm not even peddling my services. I didn't realise there would not be a RC3 either. I can't think of any more excuses.

When somebody states "without any proper testing" I take a just a little offense considering how much time I spent on this. Note I didn't pass the DNN 5 release so don't point fingers at me. Whether DNN 5 is ready or not is not my decision.

This is open source not Microsoft. If you are complaining about testing then why aren't you testing and helping? Why not develop and "open source" mentality. I can understand people who are unable to test because they have limited technical knowledge, but it seems generally the blow-hards are the people who do the least testing who complain the most.

We had virtually no feedback from the community about upgrades with the RC's, and if you think I'm gonna be testing every upgrade scenario you better pay me. ....and no I don't blame the community (otherwise I feel I would be blaming myself).


Thanks.

p.s. I think it's fair point about "release warning".