Sunday, November 12, 2006

Good bug reports

Any committer will tell you that it's important to fill out a good bug report so that he/she can quickly identify and solve the issue. What is a good bug report? One that includes error messages, stack/trace dumps, screenshots, steps to reproduce, versions of Eclipse and plugins in use, and anything else they'd need to know to find the problem. In fact, so many bugs are filed with missing information that committers have asked me to create a Bugzilla bug entry template. Great idea.

Keeping this in mind, I got a good laugh from this vague bug report, opened by none other than -- you guessed it -- an Eclipse committer ;-) So committers, please keep this in mind the next time you see a vague bug report and are tempted to close it as INVALID -- it may be your own ;-)

1 Comments:

Anonymous Eugene Kuleshov said...

I am sorry to say, that while such wizard seem a good idea for developers, it will effectively kill any users enthusiasm for submitting bug reports.

10:08 AM  

Post a Comment

<< Home