getting meta-data out of patchwork

Andy Doan andy.doan at linaro.org
Thu Mar 24 01:01:43 AEDT 2016


On 03/22/2016 10:41 PM, Jeremy Kerr wrote:
> Hi Stephen,
>
>> Is there anyway to get statistics out of patchwork about how long
>> patches sit around, reject/accept rates, and patch sizes?
>
> There's no exposed interface for stats at present, but if it's a
> once-off on patchwork.ozlabs.org I'm happy to do a query. For more
> general stuff, we can certainly looking at adding a report to the
> patchwork UI.
>
> Note that we don't (currently) track 'log' data (ie, when updates
> actually occurred), so there's no way to tell (for example) if a patch
> was accepted on the day it came in, or three months later.

We had a similar thing at Linaro. My solution isn't great, but I 
basically keep a "last_state_change" attribute and then use 
"last_state_change - date" to get time-to-acceptance[1]. This doesn't 
necessarily give a good metric, because its not taking into account a 
patch going through multiple revisions. That, however, might be a 
separate issue to tackle.

Do you guys think something like a "last_state_change" attribute would 
be worth adding models.Patch?

1: 
https://git.linaro.org/infrastructure/patchwork-tools.git/blob/HEAD:/linaro_metrics/models.py#l203



More information about the Patchwork mailing list