http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167
--- Comment #146 from Paul Poulain <[email protected]> --- (In reply to comment #143) > (In reply to comment #126) > > Hi Paul and Jonathan, I know that you have put a lot of work and thought > > into this, but it is a big change in a critical area. I would like to see > > this pass QA first before being pushed. 1 day (tomorrow, if you want to push > > on Thursday) seems a very short amount of time for the QA team or for anyone > > who wants to follow your test plan. > > If we deviate from the standard workflow, please check with the community or > dev list first. Note also that many hours have been spent on QA+ing several > versions of this development, but it never reached the final status yet > (although I certainly hope that it will!). As I've announced already, i'll be afk for 3 weeks, on friday. passed QA or not, I think/feel it's unwise to push such a patch just before leaving. If something goes wrong, everybody will be scared (including me !) So I won't push this patch before coming back from holiday. (In reply to comment #145) > > Should this be an assignment? Note that I also corrected this before. > > Maybe too fast. Seems to be corrected by another patch... I hesitated to squash all patches or have follow-ups to clearly point the differences. I choose to keep follow-ups. I feel this question is an unsolvable one... both options have their advantages and their limits... -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
