[RE]Re: [ge-talk] Bug reporting

[Michael Phipps]

How about something simple... SF, for example, allows you to set up email 
accounts for projects. gmail is free, as are several providers. You could 
easily set up an account for each app. If you know a little scripting, you 
could even pop the mail and load the results into a database. Going 
overboard, you could even set up a simple, PHP based web interface to it so 
you could see frequency of bugs, etc. Figuring that you could trigger on 
position in the code when it crashes...

Thomas Winwood wrote:
> Some way of automating the check as to whether the bug is a known one is
>  a good idea - perhaps have the e-mail sent to an automated system that
> builds a list of common crashes (so it has a typical set of crash data
> together with how many times that crash has been reported as a
> percentage of total responses) which the developer can browse through
> and see which are the major recurring bugs people experience. There'll
> probably be a long tail of rubbish (just random unreproducable crashes
> that people have mistakenly sent in) though... perhaps filter it so it
> displays only those that have been reported a minimum number of times.
> 
> Alexander G. M. Smith wrote:
>> Good point about the mail deluge.  Maybe the software should have some > way of identifying the crash and check a web site before sending the
>> crash log in. I wonder what Microsoft does with their crash > collections.
> _______________________________________________
> glasselevator-talk mailing list
> glasselevator-talk at bug-br.org.br
> http://www.bug-br.org.br/mailman/listinfo/glasselevator-talk
>