Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm gonna get downvoted for this, but... Am I the only one who disagrees? To me this post should be titled "How not to file a bug for an open source project"ยท

A good bug report should include:

- A reproducible test case - ALWAYS

- Expected output and failed output

- The exact version of the software in question (preferably git commit hash or equivalent). "Whatever shipped with ubuntu 9.04" is not a version number.

- This is optional: A patch to fix the issue

In this case the patch should have also included objdump (or similar) dumps of the libraries the author has and a list of all functions exported that should not be (e.g. everything not ^mysql_.*).

Although this bug report is valid and describes a real issue, it has to be manually confirmed as an issue by a dev. This will take 5 or so minutes, which is too long to handle any significant volume of bug reports.

I'm sure MySQL/Oracle has commercial support available if you need service. If you need help from the open source community you need to be a part of the community and do your part of the job - you're not a paying customer. A well reported bug is a half fixed bug.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: