[Koha-devel] [QA] QA process

[Marcel de Rooy]

+1 for gentle nudges :)

If A at B writes a patch and C at D signs off, I would not mind E at D to do qa. 
I think we should prevent: A at B writes and C at B signs off and D at B wants to do qa. (Reading back, the B is completely incidental :) 

Marcel

-----Oorspronkelijk bericht-----
Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Katrin Fischer
Verzonden: maandag 3 december 2012 8:09
Aan: koha-devel at lists.koha-community.org
Onderwerp: Re: [Koha-devel] [QA] QA process

Hi all,

rereading this thread again I think we can agree on the following workflow:

If a patch is not passed QA for a longer time, the developer or party can leave a note on the bug or send mail to the mailing list as a gentle nudge to the other QA team members.

If a patch is not passed QA for one month, then the patch can be QA'd by the same party. This doesn't mean of course that the RM can still ask for a second sign-off for a big feature or something he worries about.

I am going to add this to the wiki.

Katrin


_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/