In my opinion, a good bug report contains also a good description of the fix itself. In your example, you just hint at the problem.

The developer fixing the bug should have clearly said that the cause of the problem was his own version of strcpy() that didn't nul-terminate the strings.

- Michael

-- Anonymous, November 22, 2000

Answers

Good point!

FogBUGZ has integration with CVS, so in real life, that example would have included a link to a page showing the exact diff that was checked in to fix the bug.

-- Anonymous, November 22, 2000

CVS diffs not enough

Just getting the CVS diffs doesn't really say what the problem was and what you did to fix it unless you happen to be really good about commenting your code. If reading code was easy, maintenance would be a snap -- it isn't.

-- Anonymous, November 28, 2000

How do I report a bug about the bug-tracking system FogBUGZ? It'd be a good idea to set up a publicly-accessible bug database for people to report FogBUGZ bugs.

For instance, the FogBUGZ web-based tool is not easy to use in Netscape on the Macintosh because 8pt type is nearly illegible in this particular browser. A simple change to the CSS solves this bug:

Old CSS:
.navtop { font-size:8pt;font-weight:bold; color:#0000C0; text- decoration:none; font-family: Tahoma,Verdana,Arial,Helvetica;}

New CSS:
.navtop { font-size:10pt;font-weight:bold; color:#0000C0; text- decoration:none; font-family: Tahoma,Verdana,Arial,Helvetica;}

-- Anonymous, November 23, 2000

Better yet, change the CSS to specify fonts proportionately -- then the user can decide how large *he* likes it.

-- Anonymous, November 26, 2000