I, for one, would like a new bug status "updatedatabase.pl in conflict". A bit less harsh than "failed QA" and "failed signoff" (which I like, btw). :-) Any way to search the bug database to find how many "Failed QA" are caused by updatedatabase.pl not merging? This is really a dumb dumb file and process. Philippe On 03/04/2015 07:39 AM, Nicole Engard wrote:
Hi all,
I'm at the hackfest right now and have found an interesting problem with our statuses. I find a lot of bugs that are in a status of needs signoff but have conversations going on after the patch has been submitted. I feel like we need another status in here. Kyle suggested something like 'failed signoff' which isn't quite 'failed qa' but it does mean something has to be done to the patch before it needs signoff. I'm not picky - but I've found a lot of these such bugs this week and feel we need some way to remove these from the 'needs signoff' list to make it more efficient.
Suggestions? Comments? Feelings?
Nicole
_______________________________________________ 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/