| 1 |
Seemant, |
| 2 |
|
| 3 |
Hopefully you've seen the original of this, but there was one point I wanted |
| 4 |
to cover in my "Newbie's Guide to Testing": |
| 5 |
|
| 6 |
> And... How do we report bugs, which information is actually useful? And |
| 7 |
> do we report succesful installations too? |
| 8 |
|
| 9 |
I'm planning to tell people about Bugzilla, but I could use some advice on |
| 10 |
what information should be included. |
| 11 |
|
| 12 |
Obviously, platform, amount of memory, parameters passed (whether USE flags |
| 13 |
or options passed to a program, and the holy grail of all bug-killers, a |
| 14 |
reproducible problem) are all good. Anything else that would be generally |
| 15 |
useful to ebuild-writers? |
| 16 |
|
| 17 |
|
| 18 |
Second, the question about positive results is pertinent. I've seen some |
| 19 |
authors request emails to themselves. The author opening a bug in Bugzilla to |
| 20 |
hold reports also strikes me as a useful possibility. Any preferences? |
Archives