Why was a kernel-2.6.34 pushed to updates that had un-addressed bugs.

Dennis J. dennisml at conversis.de
Thu Sep 2 12:17:44 UTC 2010


On 09/02/2010 12:35 PM, "Jóhann B. Guðmundsson" wrote:
> To actually see the extent and identifying problem(s) and regressions (
> you could notice reporting trends with components ) and deal with it
> accordingly we need to gather and make public bugzilla stats for
> components.
>
> Making those stats public ( pretty sure you can easily gather them in
> bugzilla ) is more a political issue then technical one.

What I would like to see is a distinction between regressions and other 
bugs. There are a least two reasons why this might be worthwhile:

1. Regressions break functionality that has been known to work previously 
and the users already rely on. If new stuff gets added and has bugs that is 
not as serious because users are not yet relying on this to work.

2. Regressions can be easier to fix because you have a "known to work" case 
you can use as a comparison. If bugs could be flagged as regression then 
developers you potentially look at these first right after the regressions 
occurred and probably identify the reason for the regression right away.

Regards,
   Dennis


More information about the test mailing list