[sldev] Community QA process
lists.secondlife.com at trap.wereanimal.net
lists.secondlife.com at trap.wereanimal.net
Fri Apr 24 06:45:27 PDT 2009
On Thursday 23 April 2009 11:53:58 am Robin Cornelius wrote:
>
> I think also we need to monitor the crash rate and the bug reports
> coming in. In theory once all bugs of a certain severity or greater
> are tackled and the crash rate has reached an appropriate lull we can
> declare "good enough". Really incomming crash reports should be
> opening new pJIRAs so as we don't have data from this side of the
> firewall, would be good to have someone from LL open them with the
> stack traces and some indication of volume so this can be used to
> judge severity. This should cause a feedback loop that the output of
> can be used to flip the go switch.
>
How does on enter a crash report on the pjira? I've tried a while back to
report one of thousand of random crashes everyone is complaining about and got
chew out for reporting it.
Is there a guide for posting gdb bt to the pjira? What gdb commands output
would the programmers like to see?
--Techwolf Lupindo
More information about the SLDev
mailing list