It's pretty rare that I come across a bug in MySQL, but the few times I have I'm impressed at the kind of response that comes from the developers. Yesterday's bugs (filed late last night) were verified by mid-morning. I had marked both of them as severity S3 (non-cricical) but turns out one is reclassified as S1 (critical) because it's causing a server crash (as opposed to a client disconnect as I thought). It seemed trivial, a connection loss caused by a syntax error on setting up disk-based storage. Then again, nobody wants to fear that if they type their SQL incorrectly it might bring the server down.
I guess verification and resolution are two different things, but it's nice to hear back quickly. I'm glad these aren't happening in a production environment because I'd be hoping for verification and a fix by now.