On Wed, Sep 14, 2005 at 04:38:04PM +0100, Ciaran McCreesh wrote: > On Wed, 14 Sep 2005 09:42:43 +0200 Thierry Carrez <[EMAIL PROTECTED]> > wrote: > | Before debating if the QA team should have more power to enforce, > | let's just have a proper QA project. Apparently not much devs want to > | do QA, not sure telling them they will do QA+police will help in > | motivating them. > > Part of the problem with that is that people who *would* normally do QA > think it's pretty much futile right now anyway, since the worst > offenders just carry on breaking things no matter how often they're > asked to stop...
I'd agree; this is the reason I stopped auditing eclasses a year back. We've had bugs where flat out invalid deps (DEPEND dependant on has_version calls) sat for 2 years, *despite* QA/portage devs laying it on thick that this is totally invalid. That's not even getting into user complaints. There are people doing QA, the problem historically has been getting people who don't care to fix their stuff. That's a *really* quick way to burn out people doing QA; the fact that there is a problem, but they have no means beyond nagging to get the offender to fix their mess. There's only so much nagging one can do before they say "screw it", and wander off to do something a bit more productive. If QA actually had some power beyond a pissed off member complaining to devrel, I'd expect you would see those burnt out by past attempts starting again. I'd be game for resuming auditing of eclasses, personally. ~harring
pgpXJE0VcrbNg.pgp
Description: PGP signature
