I'd say it should be evaluated on a per-bug/patch basis. Overall I agree, but let the QAM and the RM have the final word about the bugs qualifying for this proposed fast-track treatment.
I will add this to tomorrow's agenda for formally talking about this. 2015-08-20 12:44 GMT-03:00 Jonathan Druart < jonathan.dru...@bugs.koha-community.org>: > I should have added that I can engage my own responsibility and will > provide a fix as quickly as possible if the patch introduced a > regression or was buggy. > > 2015-08-20 15:03 GMT+01:00 Marcel de Rooy <m.de.r...@rijksmuseum.nl>: > >> So I suggest that for some patches, the ones with a minor severity, > >> small or template changes could, IMO, bypass the signoff step. > > > > This idea comes up every now and then (just as we see our queues growing > and slinking again..). > > I would suggest to make the Complexity field mandatory. Some people do > not fill it. > > And if the Complexity== Trivial or String, test it yourself and put your > own signoff below. > > Everything above Trivial needs another signoff. > > > > 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/ > _______________________________________________ > 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/ >
_______________________________________________ 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/
