-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Aug 14, 2008, at 2:54 AM, Martin v. Löwis wrote:
As long as we're touting tools or processes that we have experience with, Google uses a combination of tools. One tool is similar to the buildbots, running tests *after* stuff has been checked in. A feature that buildbot is missing is that it tries to figure which checkin is responsible for a particular failure, and mails both the author of that change and the owner of the code (if different).
Buildbot does have a blame list. Mailing the developer failed so far because we didn't have email addresses of each developer. Now, with the python-committers list, Brett collected them, so such mailing would be possible.
I'm not sure about mailing the owner of the code: we don't typically have owners of code, right? Would you consider it useful to support the case were we do have an owner? Such an ownership database would need to be maintained, as well, and typically, when we do have owners, the owner is also the committer.
I'm not in favor of code owners, but commit owners might be
worthwhile. If we have the email addresses now, and can easily enable
it, then I think we should have the buildbots email both this mailing
list and the owner of the commit when things break.