QA Advance Volunteer List?

Carlos Leonhard Woelz carloswoelz at imap-mail.com
Thu Mar 4 07:01:00 CET 2004


On Wednesday 03 March 2004 17:09, Jamethiel Knorth wrote:
> As far as I could tell, Bugzilla did not do exactly what I was asking for.
> For example, I am a QA tester, I go over Konqueror and decide it is
> error-free. Where do I put that comment? It is not a bug. The purpose is to
> make sure that QA people don't just keep checking the same app over and
> over and over and over again. Something like a page listing the app and who
> has said it is clean.  It can't just be an is it done/not done, it needs to
> allow people to see who has okayed it, at least for generic testers.
>
> Maybe people with higher privileges (the people with CVS commit rights)
> would be able to declare an app 'Done for release X.X.X'. That is mostly
> important for right before the big releases, like 3.3.
>
> If that is in Bugzilla somewhere, I just totally missed it.

You are discussing a full QA team for KDE. Yes, I am all in favor of that. But 
we don't have the available resources. As you know, since you worked on it, 
this is no simple task.

We don't even have a proper bug management for the existing bugs. We don't 
have double checking of done bugs. I will soon put online a table for bug 
managers, one for each application, with status on the bug list maintenance, 
similar to the docs table. That will be a suitable first step. If we manage 
to build a large pool of people dealing with bugs, and solve this basic 
problems, then the first step would be to improve the system.

Thats just my view, fell free to disagree :)

Cheers,

Carlos Woelz


More information about the kde-quality mailing list