On Sun, 2007-09-23 at 12:50 +0800, Russell Keith-Magee wrote: [..] > Another approach would be to only send the failure message to the > committer that stimulated the build. i.e., you break it, you get a > nastygram in your inbox :-)
Whilst well intentioned, this tends not to work for community-oriented projects. The person who committed the change may not necessarily be available to fix it, so there's a lot of benefit to sending it to a list where the group will see it and *somebody* will end up fixing it. Also, there are a lot of way for completely random failures to happen. We've already seen this with config tweaks and timeouts (URL tests could fail due to poor network performance, for example, because we test validate_exists on the URLField). We're all helping each other here. Let's keep it that way and try to not to get held hostage too much by the green bar in buildbot. It's a guide, not a decision maker. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
