Generating stats on regression bugs in bugzilla

[Ken Sharp]

Austin English wrote:
> On Fri, Apr 24, 2009 at 6:40 PM, Scott Ritchie <scott at open-vote.org> wrote:
>> I had a theory that we might be getting better at preventing regressions now
>> than a year or so ago due to the expansion of things like AppDB and the test
>> suite.  It'd be nice to have some sort of data though.
>>
>> Would it be reasonable to comb through the bugzilla database for all the
>> bugs tagged regression and analyze them?  I'm interested in:
>>
>> 1) quantity and frequency of bugs tagged regression that were filed at
>> various dates since the release of 1.0.  I'm not sure whether it's better to
>> use the version number field in bugzilla as a proxy for "first version with
>> regression" or to just guess that from the date.
>> 2) how long regression bugs took to be fixed
>>
>> Thanks,
>> Scott Ritchie
>>
>>
>>
> 
> It'd be better to use the SHA1SUM of the bad patch, which will give
> you the day the regression was added.
> 
> If the fix has the SHA1SUM listed in there as well, it's even easier for you.
> 


Some bugs contain the wrong regression before mentioning the correct 
one.  It would be necessary to look for the last SHA1SUM mentioned in a 
bug to get the correct one.

But if the last comment is the fix... you see what I'm saying.