On Tue, Sep 22, 2015 at 01:45:25AM -0700, Martin Winter wrote: > If the major work you try to solve is tracking changes to submitted patches, > then this might work. > From the CI system integration, anything which somehow can automatically > trigger a CI on changes/submissions > etc and (preferably) receive result reports back somehow works for me. > > > Concerns about gerrit (feel free to correct/extend) > > 1) gerrit would replace patchwork, savannah and some of the quagga-dev > mailing list (discussion of the patches). > How much extra server maintenance etc is added in exchange of making it > easier to follow patches? Does > it just take some work away and replace it with other work?
And you would have to consider the potential loss of reviewers. Some people like reviewing patches on the mailing list and would hate to have to go look at some web tool instead. > 2) I somehow worry if this makes it even harder for new contributors to > figure out how to get involved. It could, and even existing contributers might not want to be involved. > 3) The discussion (which I started) was not about replacing patchwork or > code review, but mainly > about the bundling of multiple patches at the same time. This is not an > argument against any of these > tools, but I’m missing the point why reviewed/approved patches can’t go into > git immediately. What > is the advantage to bundle something like 10 patches together, review them > together and push them > together as done in the last 2 rounds by Paul? > > 4) Wow.. gerrit uses Prolog! I have distant memories working with Borlang > Turbo-Prolog. Never expected > that Prolog is still around… > > 5) Curious on other choices and their pros/cons… There are certainly a number of such tools out there. I haven't seen one I would personally be willing to use over the current system. -- Len Sorensen _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
