Thread with 6 posts
jump to expanded post
@hikari @mcepl @koopa "well" is "better than any other web-based workflow" yes, gerrit does handle them better that way.
But no way is it better than an email-based review workflow, whereby I can just tear through hundreds of patches in a very short amount of time, all while sitting behind a very slow/laggy internet connection, or totally disconnected (i.e. better for distraction-free work).
As almost no other project is at the rate of change or size of the Linux kernel, gerrit might be wonderful for your smaller one. But for ones that are our size, realize that centralized workflows like gerrit and the like just do not scale at all.
But no way is it better than an email-based review workflow, whereby I can just tear through hundreds of patches in a very short amount of time, all while sitting behind a very slow/laggy internet connection, or totally disconnected (i.e. better for distraction-free work).
As almost no other project is at the rate of change or size of the Linux kernel, gerrit might be wonderful for your smaller one. But for ones that are our size, realize that centralized workflows like gerrit and the like just do not scale at all.
@gregkh @mcepl @koopa oops I think I broke the thread continuity when trying to fix an orphan chain on my server, sorry about this
I hadn't considered the offline versus online aspect, but I think you're dead-on with that. it's too centralised and that does match with all my pain-points honestly. thanks for the insight