Bug #5732 mysqlbug script still reports to list (ignoring bugs.mysql.com)
Submitted: 24 Sep 2004 13:49 Modified: 25 Sep 2004 12:05
Reporter: Arjen Lentz Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S4 (Feature request)
Version:any OS:Unix
Assigned to: CPU Architecture:Any

[24 Sep 2004 13:49] Arjen Lentz
Description:
The scripts/mysqlbug still reports to mysql@lists.mysql.com
The messages end up in bugs@lists.mysql.com, probably a procmail rule has been put into place.

However, these bugs get lost as all our devs/support people expect bugs to show up on bugs.mysql.com.

How to repeat:
See scripts/mysqlbug in any mysql-* bk tree.

Suggested fix:
Two options:
a) Write filter on bugs@lists.mysql.com that puts these messages into the bugs db, as the fields in the message are pretty well defined.

b) (preferred option)
Modify the script to write all the (useful!) information about the system to a file, and then tell the user "here is a file containing that info, and now please go to bugs.mysql.com to report the bug. Thanks".
[25 Sep 2004 7:22] Sergei Golubchik
Not a bug. Developers still monitor bugs@ list (at least I do :)
and considering the amount of traffic that mysqlbug generates it's not worth the troubles to rewrite it, better to have new GUI tools to report to bugdb
[25 Sep 2004 12:05] Sergei Golubchik
reopened as a feature request