Brian,

  In several cases these are issues that we have discovered on DotNetNuke.com.  Unfortunately we have not always been completely dilligent about documenting the issue in Gemini.  The automatic upgrade bug is a perfect example.  This actually cropped up one morning and locked everyone out of DNN.com.  We resolved the immediate issue and then Shaun, Charles and I got on the phone to triage the problem/solution.  Given that the bug took DNN down for a couple hours it was high on the priority list to fix the bug.  Which happened that day.  I don't think anyone actually looked in Gemini to see if it was already logged or even to log the fix.  That is certainly a problem, and one we need to do a better job of avoiding.

I cannot speak about every bug, but in general that is why you will find bugs/enhancements or whatever that get slipped in - because we are having some issue that needs resolution so we make the fix.  Sometimes we remember to get it in Gemini and sometimes in the excitement it gets lost.

Great Job.   I'm very pleased to see so much more....

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=5645     this is one that I mentioned, very happy to see it fixed

Brian,

As Joe stated some issues are fixed becuase of their severity before being logged into Gemini, or the issue is reported in the forums and a core team member ends up figurig out the fix when answering the forum.  Sometimes these do slip by and are not entered, but all the core team members / project leader as better than they were a year ago and will continue to do this out of habit.  Overall Gemini is the most current than it has been in the past year and we we will continue to improve the processes  to make this easier on everyone.

As far as issues that you personally reported that are related and/or dupicates of issues that have been fixed please send me a list of these items.  Please include the issues number, the issue number it is related to, whether your issue is a duplicate or related link.  If the issue is fixed but not in the log I also send me those in the list.  I will do some get them updated as being fixed in 4.5.2.