Folks,
We are, in general, using asciidoc for documentation. And this is good.
Special case: build.txt. Should this be in clean text, no markup at all (the person reading may not know he needs asciidoc till after he reads it)
Or should it be in plain text, and then we lose out somewhat on the beauty of subheadings, bullet points (search for "pps=yes". This (and following) lines would be easier to understand if it was bulleted, but someone might assume the leading "." was part of the option.)
Or we could ship a build.html, in the release tarball?