Why vote so low for DNN7 release

Actually everyone was looking forwards to DotNetNuke7, which should be equal to the so-called milestone, however, more expectations more disappointed. Let us take a look at the votes in codeplex – until today only average 2.8 rating with lots of lowest 1 star:

Was updating from v.5.5.1. When updating all files I get the following error when updating (Install page) DotNetNuke Error An unhandled error occurred. < Back to website Can I look at my error logs somewhere? Regards, Ely

Having major problems adding new modules - when adding a module with multiple definitions only the first control is output. It's also annoying when adding/updating module definitions (or modifying settings in general) - the section of the page keeps collapsing every time a change is saved.

Some good ideas, and as always we encourage the had work of those who have put into this release. Well done... but for those who are thinking of running this version. Forget it! Significant bugs that are show stoppers that no doubt will be fixed fast!

'Fixed issue in the Journal that made image thumbnails not clickable' NO YOU DIDN'T!!! This makes the Journal module useless unfortunately.. Everything else looks good, thank you for the great release and all the hard work you put in.

You can find more similar comments there. In this scenery we may have some questions. Is it the stable version with so many issues? When will the next fixed version be available? Why introduce so many bugs?…  This buildings indeed included tons of enhancements, especially in the look and feel, but meanwhile we still need to provide workable product to community, right? Not only we need small iteration development but also require quick response. In the end, I want to express my real feelings that we like DotNetNuke much and hope it run better and better but hope that it will be more stable & lightweight again; plus, it will better if some key features may be included in community version. :)

BTW, you can fix the second issue mentioned above by switching to the original control panel "RIBBONBAR" in the host settings but not the new one, which looks nice but not useless. I ever mentioned this workaround in another post - SunBlogNuke v5.6.2 works well with DNN7.