Reindl Harald writes:
Am 20.05.2013 12:35, schrieb James Hogarth:
> Did you read his later message? he found the bug already reported 18 months
> ago complete with proposed patch, verified status and S2 (serious) severity
> ... and yet not fixed...
and how does this match his "I find nothing but Oracle's bureaucratease,
when I
try to dig around mysql.com" while type "mysql bugreport" would be enough
to get to
http://bugs.mysql.com/?
Can you go to
mysql.com, type "mysql bugreport" in the search box on the
top, and see what you find.
I wouldn't expect a need to use Google to figure out where to report mysql
bugs, when mysql's home page, presumably, exists, and that's where one would
logically expect to look, first. Maybe if I didn't know what mysql's
homepage was, perhaps, then I can understand using Google. But not when,
allegedly, mysql has a home page that I can look at.
By comparison, if I go to
www.postgresql.org, I immediately see a fscking
"Report a Bug" link right on the home page. Was that too hard?
The closest thing on
www.mysql.com is the "Contact Us" link. That leads to
Oracle's sales department. An even tinier link, at the bottom, called
"Support" leads to a gateway for paid Oracle technical support.
And even if one would like to make an argument that using Google would not
be unreasonable here, it's still reasonable to expect that the best place to
find the relevant link would be the home page, but after looking around
www.mysql.com, you can't blame someone for getting the impression that it's
going to be a waste of time.
Furthermore, the fact that the bug remains unfixed, even with a supplied
patch, isn't a good sign.