Hi,
There are two possibilities, in this case:
1) the bug was fixed, but the patch was not pushed by mistake.
2) the bug was fixed in an earlier version, and now it's broken again.
To verify the above, you should check if version 5.0.30 passes the test, while later ones don't.
If you find that no version from 5.0.30 till the current was patched, then a mistake has happened. In this case, send a message to the internals mailing list, and to me as well (my first name at mysql dot com).
If it was fixed in 5.0.30 and now the buggy behavior is there again, then it's a new bug. You can submit a new one, mentioning that it was already reported and fixed as Bug#21635, but it is again showing up in the current version.
Best regards
Giuseppe
--
Giuseppe Maxia, MySQL Community Team Leader at Oracle
http://dev.mysql.com