Bug #28368 Change log probaly not complete : missing bug 27513 report
Submitted: 11 May 2007 8:16 Modified: 11 Jun 2007 12:00
Reporter: Henk Wetering Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.40 OS:Any
Assigned to: CPU Architecture:Any
Tags: 27513 changelog

[11 May 2007 8:16] Henk Wetering
In bugreport 27513 it states the (security) patch is pushed into 5.0.40. Unfortunately this is not mentioned in the changelog for the new version span from 5.0.37 to 5.0.40.

There are various reports on the internet by security companies the bug is fixed in 5.0.40 but there is no official confirmation by MySQL.

How to repeat:
Read the bugreport 27513. Read latest changelog. Compare both. No match is found.

Suggested fix:
If this bug was fixed, pleas update the changelog accordingly.
[11 May 2007 12:00] Valeriy Kravchuk
According to the last comment in bug #27513:

"[9 Apr 21:26] Paul DuBois

Test case change only. No changelog entry needed."

there was no need to add this bug to changelog, as we simply added a test case to our regression test suite to chec for that bug. As 5.0.40 was released officially, it had passed all the regression tests successfuly. So, this bug SHOUL NOT be present in 5.0.40. If you have any evidence thts bug is still present, please, send it.
[11 Jun 2007 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".