diff -r 467285511629 buildbots.rst
--- a/buildbots.rst	Mon Jun 08 22:43:52 2015 -0500
+++ b/buildbots.rst	Thu Jun 11 17:32:27 2015 -0400
@@ -26,7 +26,7 @@
 Checking results of automatic builds
 ------------------------------------
 
-There are two ways of visualizing recent build results:
+There are three ways of visualizing recent build results:
 
 * The Web interface for each branch at http://python.org/dev/buildbot/,
   where the so-called "waterfall" view presents a vertical rundown of recent
@@ -42,6 +42,24 @@
 
       bbreport.py -q 3.x
 
+* The buildbot "console" interface at http://buildbot.python.org/all/console
+  (this link will take a while to load), which provides a summary view of all
+  builders and all branches.  This works best on a wide, high resolution
+  monitor.  You can enter the your mercurial username ("your name
+  <your@email>") in the 'personalized for' box in the upper right corner to see
+  the results just for changesets submitted by you.  Clicking on the colored
+  circles will allow you to open a new page containing whatever information
+  about that particular build is of interest to you.  You can also access
+  builder information by clicking on the builder status bubbles in the top
+  line.
+
+If you like IRC, having an irc client open to the #python-dev channel on
+irc.freenode.net is useful.  If a build fails (and the previous build by the
+same builder did not) then a message is posted to the channel.  Likewise if a
+build passes when the previous one did not, a message is posted.  Keeping an
+eye on the channel after pushing a changeset is a simple way to get notified
+that there is something you should look in to.
+
 Some buildbots are much faster than others.  Over time, you will learn which
 ones produce the quickest results after a build, and which ones take the
 longest time.
@@ -83,7 +101,7 @@
 Ordering-dependent failures
 ---------------------------
 
-Sometimes even the failure is subtler, as it relies on the order in which
+Sometimes the failure is even subtler, as it relies on the order in which
 the tests are run.  The buildbots *randomize* test order (by using the ``-r``
 option to the test runner) to maximize the probability that potential
 interferences between library modules are exercised; the downside is that it