Hi, the QA workflow usually requires two sign-offs, one from a QA team member. Sometimes the QA step requests some major changes to the patchset, which is usually added in a followup patch, and it is considered that a new sign-off step is required. Then you have (most of the) patches that are signed off, but the bug marked as NSO. Hope it helps. Maybe this link has valuable info: https://wiki.koha-community.org/wiki/Development_workflow Best regards El mié., 29 ago. 2018 a las 9:37, Cab Vinton (<bibliwho@gmail.com>) escribió:
Every now & then I come across a bug that's been signed off, but the status is still "Needs Signoff" (e.g., https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14493).
Can someone explain?
Guessing maybe patches need multiple sign-off's before they pass QA?? If so, probably from someone higher up the food chain than a regular end-user like me?
I didn't find guidance in the Development Workflow wiki, but I might have missed something.
Many thanks,
Cab Vinton, Director Plaistow Public Library Plaistow, NH _______________________________________________ Koha-devel mailing list Koha-devel@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/
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F