Re: Patchwork & patch handling improvements

[Koen Kooi <koen@dominion.thruhere.net>]

Op 26-11-15 om 22:00 schreef Paul Eggleton:
> Hi all,
> 
> Over the past several years one of the regular complaints people have made 
> about our project has been that patches sometimes take a long time to make it 
> into master, and it's not always clear what the state of a patch is during 
> that time. On the other side of things, maintainers are finding it increasingly 
> hard to keep up with testing and integrating incoming patches. Additionally, 
> trivial mistakes sometimes creep in that would be fairly easy to catch with an 
> automated process. We've been talking about this for a while and now I'd like 
> to propose a plan to finally address this:
> 
> 1) Upgrade the OE Patchwork instance [0] to a newer release; this should fix 
> some of the problems we are having [1] plus give us additional features. I 
> propose using the fork that freedesktop.org are using [2] [3] which is moving 
> a bit faster than upstream Patchwork; whilst the changes there may eventually 
> make it upstream (and work is ongoing there) we have a much greater ability to 
> influence the fork given that it's being worked on by one of my colleagues who 
> is pushing it in the direction we need it to go e.g. proper support for series 
> as opposed to treating every patch individually, improved UI, etc.

I very much support upgrading patchwork to the fdo version, the set-aware
feature removes a lot of visual clutter.

regards,

Koen