summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2009-08-01 19:25:25 +0000
committerChris Lattner <sabre@nondot.org>2009-08-01 19:25:25 +0000
commitd7f10d33610fbf226e6e9425c534d0914fd012d4 (patch)
tree8349990ab0311bbe4f3b0df9b1f877cc8a054bb5 /docs
parent7e77b0fcb0d00309ab59ad167becf203e61b2aea (diff)
downloadllvm-d7f10d33610fbf226e6e9425c534d0914fd012d4.tar.gz
llvm-d7f10d33610fbf226e6e9425c534d0914fd012d4.tar.bz2
llvm-d7f10d33610fbf226e6e9425c534d0914fd012d4.tar.xz
add a note about the build bots
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@77796 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r--docs/DeveloperPolicy.html9
1 files changed, 6 insertions, 3 deletions
diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html
index 9c8b4d666b..dd201848b2 100644
--- a/docs/DeveloperPolicy.html
+++ b/docs/DeveloperPolicy.html
@@ -287,9 +287,12 @@ svn diff
</ul>
<p>We prefer for this to be handled before submission but understand that it
- isn't possible to test all of this for every submission. Our nightly testing
- infrastructure normally finds these problems. A good rule of thumb is to
- check the nightly testers for regressions the day after your change.</p>
+ isn't possible to test all of this for every submission. Our build bots and
+ nightly testing infrastructure normally finds these problems. A good rule of
+ thumb is to check the nightly testers for regressions the day after your
+ change. Build bots will directly email you if a group of commits that
+ included yours caused a failure. You are expected to check the build bot
+ messages to see if they are your fault and, if so, fix the breakage.</p>
<p>Commits that violate these quality standards (e.g. are very broken) may be
reverted. This is necessary when the change blocks other developers from