Tracking auto-tester regressions better through bugzilla bugs

[Daniel Berlin]

Just so nobody thinks nothing came of this suggestion (it was mentioned 
during one of the steering committee Q&A questions), i'm working on 
making a way for the auto-testers to be able to submit new regressions 
by email (in an easy-to-parse format, possibly XML based) to an email 
address, and it will automatically create a new bugzilla bug to track 
the regression, and auto-cc the people who could be responsible for it.
It'll be smart enough to not create more than one bug per regression, 
smart enough to auto-add a new "this also fails on platform x" comment 
to the bug for auto-testers that discover the same regression on a 
different platform.

I thought i should mention it here, in case someone is incredibly 
adverse to being occasionally cc'd on a bug they had nothing to do 
with, simply because a regression occurred because of the few patches 
committed around the same time as
Speak now, or hold your peace until the auto-testers can narrow down to 
the exact patch that caused the regression.

--Dan