Bernd Eilers, 14-03-2005 10:37:

A report with a description in any language the developer handling the report does not understand is as good as report without a description at all. There is no translation step handling dozens of different languages involved in processing the reports. Later is also something which could not be handled by the community as there are privacy concerns involved, we simply do not want to make the report data readable to everyone.


As the one who is responsible for the program doing the backend proccessing of those reports I can say that MOST of what we get does not contain any useful description at all anyway. Reproducable step by step instructions are really the exception. Most users simply leave the description field empty or have only very few text in there like "I was editing a textdocument", "the dammed thing crashed again" or similar. It sometimes would be good if we would get better descriptions but in most cases the technical information about the crash is enough. There is altough a class of reports where the technical information send with the report does not help at all in fixing the bug (that maybe the case for round about 5% of incoming reports) and in these cases useful step by step instructions would be very helpful, of course. But for this class of reports also grouping together similar reports based on the technical information send is impossible resulting in a very low priority of trying to handle them compared to other reports where a high frequency of occurance of the same issue can be assumed.

PS: Bye the way, if you have a crash, send the crash report and additionally are going to file an issue, please do not paste the data of the crash report into the description! We do have a problem with the XML frontend for issuezilla if an issue description does contain XML tags. If you want to add crash report data to an issue, please create an attachment instead.


Thanks a lot by making it clear.
The most of users who use the crashreport and don't file issues don't know how to describe it step by step. Sometimes it's just a matter of hard/software incompatibility.
In such cases I just send the crashreport with no/a few description, as I know the most important is the data it sends.


We could say: "if you can't write it in english or german you can let this field empty, as it's optiional" (or something better, english is not my primary language).


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to