[sldev] Community QA process

[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 as "for anyone's  
usage" and not just devs. If we have a community QA, I think the best  
is to agree on a "level of bugs" criteria (say: no show stopper for  
instance). We can decide what constitute a show stopper on this list  
and during the weekly IW triage meeting with the community.

> Will we need to have a daily triage discussion during the last leg  
> of development?

I propose "limited to the identified set of show stoppers". Otherwise  
it'll be endless.

> Will there be anyone willing to run through formal test plans?  What  
> is realistic?

That doesn't seem very realistic to me... unless someone volunteers of  
course! :) Having lots of community eyes on the product though should  
ensure a rather good test coverage IMHO.

Then of course, we need more unit tests and auto tests (crash rate in  
particular). That could also give us a release criteria.

Cheers,
- Merov