Sorry I just had to contribute towards this....

From my perceptive I've been working on Gemini since December, have been studying it since July last year, and I and the rest of the quality team have recently gone thought a tremendous backlog of what appeared to be 2 to 3 years of backlogged issues.

It does no surprise to me in the slightest that this release had a few major bugs and I expect to see more of them for this release as time goes by. Each new version has had them. What comforts me is the situation is getting better and better, and we are getting less and less of them. We are winning the battle, but not instantly.

To get this into some perspective, in Gemini there are currently 178 core bugs that still need fixing in Gemini (they are all listed for everybody to see, go and have a look). This will take time to fix as there are limited resources... so I'm still not reassuring you very much so far am I!!! But put this into some perspective, look at the 4.4.1 and 4.5.0 releases, see the number of bugs fixed? Far far more than previous versions.

So real progress is being made and basically the core team have worked their butts of fixing them, inc Charles Nurse and they should all be congratulated. I'm hoping the next couple of releases solely concentrates on fixing the existing bugs and bringing them down to near zero, if not zero, we shall see, and it's entirely not my decision (nor should it be). However, if I had my way I would honestly say the next release should only happen when 99%  of all the bugs have been resolved, but I absolutely know that I would clearly be in the minority of opinion and this would be totally unacceptable by most of the community!

From my perspective I am glad there are just benefactor RC releases and not public BETA’s, I (I can't speak for the rest of the QA team) just would not have the resources to cope validating through all the duplicate issues being logged by the community in Gemini and we'd probably just walk out and call it a day there and then. We have enough on our plate already thanks, and we all have day jobs.

Still not happy with the situation? Fair enough then. Come back and revisit this post in six months and let's see what actually happens. Remember there are 178 core bugs right now. More will be logged, but let’s see what that total is in six months shall we?

I don’t blame people for not being happy with the situation, I wasn’t happy bunny as well in the past, see the post below to get some perspective. Please note the point here of posting this link is not to pat myself on the back here and try and get "QDOS" out of it, but to show you where I came from originally, so I honestly can understand why some people may be very unhappy. But please, try and turn this into something positiive, it is in all of our interests after all:
http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/118/threadid/91711/scope/posts/Default.aspx

Happy Easter!

I completely understand that bugs can not be equal to zero for a release. But what I am surprised about, is that an upgrade bring some new bugs. See for example the problem with FCKEditor which is not able to handle images. This is surprising for me.

Nevertheless, we can not complain, the product is globally very good (I will go back to 4.4.1 for the moment, until problems are solved, and I am satisfied with 4.4.1 which works very well).

DV

First, sometimes I am glad not to be able to comment all of the statements due to my lack of English language.

Second, I would like to thank Alex and the others on the QA team for their outstanding work.

Third, I am aware of all issues with lately added changes, that haven't been fully tested - in this case the FKEditorProvider. But please all be aware of a situation of a delayed release having issues with the new default editor, which are fixed by the project team asap as well as resonding to the demand of forum users to include the latest version of the editor. As a conclusion, there is always a tradeoff between features richness and testing level. From my perspective, the core team tries it best to find an optimal solution, though it might not be the correct decision "ex post".