[Digikam-devel] Bugzilla Bug-Tagging process

Gilles Caulier caulier.gilles at gmail.com
Sun Jul 11 11:00:54 BST 2010


Do you read this entry :

http://quality.kde.org/develop/howto/howtobugs.php

For normal users, i don't know exactly. I agree with you, this will
more simple for the team.

Gilles



2010/7/11 Andi Clemens <andi.clemens at gmx.net>:
> Hi,
>
> does anyone know if "normal" Bugzilla users at B.K.O are able to mark a bug as
> VERIFIED?
>
> It would help a lot reducing all those open bugreports.
>
> At our company we handle bugzilla like this:
>
> 1. A bug is opened by either a developer or a member of the QA team.
> 2. Bug gets fixed, developer marks it as RESOLVED (FIXED).
> 3. A member of the QA team retests all of his bugs and marks every bug as
> VERIFIED (FIXED), if the bug has really been fixed, otherwise it gets re-
> opened again.
>
> This way you get rid of open bugs quickly, and you don't have to ask all the
> time if the bug has really been fixed (normally you know that you have done it
> anyway :-)).
>
> Right now it is quite annoying asking all the time if the bug is fixed,
> especially on old bugreports where nobody is answering anymore.
>
> Andi
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel
>



More information about the Digikam-devel mailing list