Alex,
I am fully aware of how Gemini works. We use it ourselves for our development projects and have done so since 2005. I am intimately familiar with the application from an administrator level. With that said, I understand that Gemini is not for troubleshooting, although many of our users do that and we too send them to the forums, hence the reason I used the forums first.
I am not some newbie that came to the forums here without having tried some basics and doing some searches. While I have not made many post here in the past, I do make sure I look around before I post anything. In fact, if you look at my profile, I have been here a full year more than yourself, but not as active. I used this thread to see if other were having the issue BEFORE I posted in Gemini. Furthermore, the issue did NOT occur before the upgrade and did occur after the upgrade without any changes being made to the system other than the upgrade. I can understand that you could not reproduce the issue, but that does not mean it did/does not exist. According to the history of the issue, I created it at 3/18/2010 11:34:28 AM and you closed it 14 minutes later (“3/18/2010 11:48:55 AM Alex Shirley Issue status changed to Closed”), so maybe you are referring to billable hours, rather than actual hours/time when you said you spent a “good hour”. However, it was very apparent that several people were having the same issue, and no telling how many more that were just observing the thread, but the issue was closed despite other people reporting the exact same issue after upgrading. Would it not have been better to assign the burden of the issue in Gemini back to me? “Issue Submitter” is an option in Gemini and we use it for that purpose. We set the issue to “Cannot Reproduce” and assign to “Issue Submitter”. It’s not like it would have hurt for that issue to remain logged and visible for 24 hours until I was able to reproduce it. I tried 2 other upgrades yesterday afternoon and could not find the issue, before seeing Joe’s blog post about 5.3.0 being withdrawn. I spent a good 2 hours trying to fix the issue on that site and try other combinations as no one was able to register. I finally found a workround by adding a regex to the Friendly URLs. Luckily and thanks to Will, the issue was reproducible and he created a Duplicate issue in Gemini. Had my issue been still visible, he could have just posted the steps there, rather than creating a new record.
Anyway, I am not trying to break your balls, but there is no need to preach to me about how to use Gemini or the Forums. In this case, I think you were a little premature with closing the issue.