> The Enhancement was ready for Sign off on 2017-04-30, was signed off on > 2017-05-02, and, after some discussion, passed QA on 2017-10-27, and the same > day was set to "In Discussion".
Can imagine that it does not make you very happy ;) It obviously is rather sad that patches are sitting so long in the QA queue. That is a topic on itself. But in brief, imo QA takes more time than signing off and we have more people signing off than in QA. So what would you expect (unfortunately)? > After the enhancement has been put to "In discussion", I kindly ask the Koha > community to vote about Bug 18483 as outlined in: > https://wiki.koha-community.org/wiki/Bug_and_Enhancement_Discussion I do not think that a move to In Discussion should immediately trigger the procedure you describe. It could well be that after a few comments the status could be moved back to PQA (in general). Might be different here btw. On the bug itself, I saw my own comment back from a related bug 18472 in reply to Jonathan, as well as the comment of Kyle too from Oct 27. In my view there is serious doubt in the QA team if we should push it in this form. Kyle calls it "piggy backing has got me a bit iffy". I was thinking about a term as misappropriate use (hoping that this is the right translation for the Dutch 'oneigenlijk gebruik') ? So this may have contributed to the long time in the queue, and the move to In Discussion was not really "out of the blue". Hope that helps a tiny bit, Marcel _______________________________________________ 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/
