Re: [sldev] Community QA process

2009-04-25 Thread Carlo Wood
On Fri, Apr 24, 2009 at 06:01:47PM -0400, lists.secondlife@trap.wereanimal.net wrote: > install. My entire system is split-debug, so when I do a bt, it goes all the > way back. I also use -ggdb in make.conf Wow :p Make that 99.9% in my previous post - lol. I'm amazed! -- Carlo Wood _

Re: [sldev] Community QA process

2009-04-25 Thread Carlo Wood
On Fri, Apr 24, 2009 at 12:17:10PM -0400, Jason Giglio wrote: > GDB Backtrace on an *unstripped* binary, along with a little about what > you were doing when it happened, is probably enough info to fix 80% of > the bugs. I disagree. Most crashes happen in third party libraries. The crashes that la

Re: [sldev] Community QA process

2009-04-24 Thread lists . secondlife . com
On Friday 24 April 2009 12:17:10 pm Jason Giglio wrote: > GDB Backtrace on an *unstripped* binary, along with a little about what > you were doing when it happened, is probably enough info to fix 80% of > the bugs. > Due to a bug in the cmake build system, the strippped binary is not created, so

Re: [sldev] Community QA process

2009-04-24 Thread Jason Giglio
GDB Backtrace on an *unstripped* binary, along with a little about what you were doing when it happened, is probably enough info to fix 80% of the bugs. What I do to make an unstripped binary is to change the strip command in the makefiles to a cp command. This way I know it's exactly the same bu

Re: [sldev] Community QA process

2009-04-24 Thread lists . secondlife . com
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".

Re: [sldev] Community QA process

2009-04-23 Thread Robin Cornelius
On Thu, Apr 23, 2009 at 6:14 AM, Philippe Bossut (Merov Linden) wrote: > Hi guys, > > On Apr 22, 2009, at 11:40 AM, Rob Lanphier wrote: >> How will we know when we're "done"? > > I'm tempted to answer "define 'done'" though that's not very > constructive :) > I think we have a pretty well defined

Re: [sldev] Community QA process

2009-04-22 Thread Philippe Bossut (Merov Linden)
Hi guys, On Apr 22, 2009, at 11:40 AM, Rob Lanphier wrote: > How will we know when we're "done"? I'm tempted to answer "define 'done'" though that's not very constructive :) Since we have nightly builds, that notion of a done viewer only applies to "the OS viewer", the one that gets stamped

Re: [sldev] Community QA process

2009-04-22 Thread Gordon Wendt
Rob, When PN's become available for this branch will notices be posted to the BSI and/or sldev lists so that we can easily keep up with them? Thanks. -G.W. On Wed, Apr 22, 2009 at 2:40 PM, Rob Lanphier wrote: > Hi folks, > > I've filed the following issue in JIRA: > > "Write up QA process for

[sldev] Community QA process

2009-04-22 Thread Rob Lanphier
Hi folks, I've filed the following issue in JIRA: "Write up QA process for new http-texture branch viewer" https://jira.secondlife.com/browse/VWR-12931 ...which is on my plate to write up. However, I'm looking for community input on this. One thing we're not currently planning on doing is sub