BUILD and devel/STATUS files need cleanup

[Eric S. Raymond]

Hal, I guess this belongs to you as you wrote the devel/STATUS file.  And
maybe Amar as the buildbot shepherd.

Presently we have build status information in two files: BUILD (for the Mac) and
devel/STATUS (all other tested builds).  We also have a buildbot page that
has up-to-the minute info on which builds are currently good.

Here are my requests:

1. If we're going to have static build-status information, it should live in
   one file rather than two different ones.

2. Somebody who is willing to own the static status information (on previous
   discussion, probably Hal) needs to think hard about whether that page
   should live in the source tree or the project website.  I don't have
   a strong opinion about this but think the tradeoffs should be considered.

3. If the decision is to move the build status information to the website,
   the master markup will need to change to asciidoc.  If it's going to stay in
   the tree, please structure it as asciidoc anyway.

   I'm trying to get us into an all-asciidoc-all-the-time habit for two reasons:
   (1) so the in-tree documentation is uniform and easy to browse, and (2) so
   that we have options to generate nice web content from it automatically
   (though the logic for that is not yet in place).

4. Somebody (not me, I don't want to spend the concentration) needs to think
   carefully about the relationship between the static build-status info
   and the buildbot reports.  Is there any way to attach quirk notes to
   each buildbot build? If so, can the static build-status info go away?
   If not, what else can we do to reduce duplication and handwork?
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>