[Adium-devl] Better bug reporting statistics

[David Smith]

One nice easy one for someone interested (I forgot about it last  
night when I had some time for once. dang.) would be to track number  
of crashes since the last sparkle submission, and number of hours run  
in the same period. That would get us MTBF numbers so we could at  
least tell which direction stability was headed.

Long term I think crash reporting is so valuable and general purpose  
that we need an equivalent to Sparkle (or equivalent to SCR without  
using input managers). Something nicely encapsulated that we can drop  
into any project and get instant crash reports. Doing this as an  
Adium-specific project would be doing the Mac community a disservice.  
My research so far indicates that google breakpad is the obvious  
choice for a backend (with access to all of Mozilla's serverside  
tools built to go with it, see http://crash-stats.mozilla.com/ for an  
early version), but I'm open to other suggestions.

					David

On Aug 1, 2007, at 1:54 PM, Chris Forsythe wrote:

> Before I quit irc again (9th time, and it's sticking so far!),  
> David and
> I were discussing our crash logger options. Breakpad gets brought up a
> lot, but in general we've been floating around a few different things.
> The idea for 1.1 was soc2006, and 1.2 is soc2007. I'd like 1.3 to  
> focus
> on getting better crash reporting statistics, but that's just me. What
> does everyone think about making a concerted effort for getting better
> crash log stats in 1.3 so that we can start working better on those in
> general and have a better idea of longterm changes in code being
> effective for crash prevention/resolution?
>
> Chris
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com