John McCabe-Dansted wrote: > - Keytest can automatically add bisection information etc.
i would say that this is the fundamental feature, because you have commit in your hand and can give it to the responsible person. > - Keytest can provide bug reports in trunk when the code is fresh and > before the bugs have been fossilized in Ubuntu packages, whereas user > generated bug reports tend to come long after the code was written. > - The main downside of Keytest seems to be its tenancy to flood trac, > but that can be somewhat worked around by not marking obscure keytest > bugs as being highest priority. > > I was wondering if the people who actually dealt with the bug reports > agreed with this sentiment, and also if anyone wanted to voice any > view points that they would like me to include in the presentation. the machine also produces bugs which would not occur to the normal user. then you have new kind of problem - you dont want to close the bug, since it really crashes, on the other hand, there is no manpower or willingness to fix all weird corner cases. then you need to screw your brain and un-learn that any crash is critical... its rather psychological than technical issue that if keytest generate 5 bugs per week you easily break through certain threshold after which motivation to fix remaining bugs decrease. i'm sure Vincent could give you better insights ;) good luck with presentation, pavel
