On 29 March 2018 at 09:19, Magnus Hagander <mag...@hagander.net> wrote: > > > On Thu, Mar 29, 2018 at 10:06 AM, Alexander Korotkov > <a.korot...@postgrespro.ru> wrote: >> >> Hi, Fabien! >> >> On Fri, Dec 1, 2017 at 9:10 AM, Fabien COELHO <coe...@cri.ensmp.fr> wrote: >>>> >>>> And the last 21 patches have been classified as well. Here is the >>>> final score for this time: >>>> Committed: 55. >>>> Moved to next CF: 103. >>>> Rejected: 1. >>>> Returned with Feedback: 47. >>>> Total: 206. >>>> >>>> Thanks to all the contributors for this session! The CF is now closed. >>> >>> >>> Thanks for the CF management. >>> >>> Attached a small graph of the end status of patch at the end of each CF. >> >> >> Thank you for the graph! >> It would be interesting to see statistics not by patches count, but by >> their complexity. >> For rough measure of complexity we can use number of affected lines. I >> expect that >> statistics would be even more distressing: small patches can be committed >> faster, >> while large patches are traversing from one CF to another during long >> time. Interesting >> to check whether it's true... >> > > I think that's very hard to do given that we simply don't have the data > today. It's not that simple to analyze the patches in the archives, because > some are single file, some are spread across multiple etc. I fear that > anything trying to work off that would actually make the stats even more > inaccurate. This is the pattern I've seen whenever I've treid tha tbefore. > > I wonder if we should consider adding a field to the CF app *specifically* > to track things like this. What I'm thinking is a field that's set (or at > least verified) by the person who flags a patch as committed with choices > like Trivial/Simple/Medium/Complex (trivial being things like typo fixes > etc, which today can hugely skew the stats). > > Would people who update the CF app be willing to put in that effort (however > small it is, it has to be done consistently to be of any value) in order to > be able to track such statistics? > > It would only help for the future of course, unless somebody wants to go > back and backfill existing patches with such information (which they might > be).
The focus of this is on the Committers, which seems wrong. I suggest someone does another analysis that shows how many patch reviews have been conducted by patch authors, so we can highlight people who are causing the problem yet not helping solve the problem. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
