On 11/18/2015 12:38 PM, Paul Jakma wrote: > On Tue, 17 Nov 2015, Martin Winter wrote: > >> 3 days is too short for me to do actual testing. It might be ok for a >> smaller amount of patches, but >> for a large batch of like 60 patches I need more time. >> >> I.e in the current case of the 60 patches form cumulus, I know at >> least a few more errors and need some time to narrow them down and >> give useful feedback. > > So the batched system can optimised for patch-throughput, while still > leaving time for review, testing, and other bits of process. > > Is there latency, sure, but, do we really need to optimise for latency?
Yes, imho, we absolutely do need to optimize for latency. While we probably won't see patches as large as those recently submitted from Cumulus every other week, it is a burden if patches that cause merge conflicts with pending devolepments are pending for long time. These conflicts are not necessarily an insurmountable issue, but I'd rather spend time on coding that performing git acrobatics. -Christian _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
