Up a number of parents:
>that the number of patches and/or important issues in 2.6.31 exceeds that for recent releases. Is this true?
Statistically, this seems to be the case.
v2.6.16.62: 1053 commits within 854 days (avg=1.23)
v2.6.27.37: 1298 commits within 367 days (avg=3.53)
v2.6.28.10: 613 commits within 128 days (avg=4.78)
v2.6.29.6: 383 commits within 101 days (avg=3.79)
v2.6.30.9: 436 commits within 118 days (avg=3.69)
v2.6.31.6: 372 commits within 61 days (avg=6.09)
>If so, are there any lessons to be learned?
Also see it from the other side: rather than 2.6.31 being overly buggy, we just give it more bugfixing love than the previous ones.
Posted Nov 13, 2009 6:52 UTC (Fri) by njs (subscriber, #40338)
[Link]
Your statistics are only valid if the patch rate for each stable series is constant over time. It seems more likely that patches flow in the fastest at the beginning of the stable series, and then the rate drops off over time. If that's the case, then your calculation will always show the most recently released kernel as being the worst, because it's the one that's still in that early part of the cycle. Better would be to compare the same period (the first 61 days) of each kernel.