Jared,
Could have missed something, but was this decided recently?
The additional signoff will mean more workload for the QA team, since it 
requires additional testing. Which is fine of course in theory, but may lead to 
a larger queue of patches waiting for QA, etc.

Marcel

Van: [email protected] 
[mailto:[email protected]] Namens Jared Camins-Esakov
Verzonden: vrijdag 23 november 2012 18:20
Aan: [email protected]
Onderwerp: [Koha-devel] [QA] QAing and signing off

Hello.

Now that the 3.12 release cycle has officially begun, I would just like to 
remind the QA team to sign off on patches when they are QAing. I will 
"grandfather in" the patches that were already QAed with a signoff, but I will 
not push any more patches after the ones that have already passed QA without a 
signoff from a QA team member.

Regards,
Jared Camins-Esakov

--
Jared Camins-Esakov
Bibliographer, C & P Bibliography Services, LLC
(phone) +1 (917) 727-3445
(e-mail) [email protected]<mailto:[email protected]>
(web) http://www.cpbibliography.com/

_______________________________________________
Koha-devel mailing list
[email protected]
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/

Reply via email to