Junio C Hamano <gitster@xxxxxxxxx> writes: > Stuart, is there anything we can help you to set up some automated > tests to catch AsciiDoc regression, so we do not have to suffer like > this again? We considered adding a nose test suite. The upcoming v9.0 release involves quite a bit of code massaging and we will definitely need an extensive test suite. But the test suite can only catch obvious rendering failures so any help in eyeballing the output will be appreciated. Should we setup a distributed proof reading system like Project Gutenberg? I hope we don't need it. But a few scripts to batch render all the doc of popular projects would be nice. We could upload such snapshot render jobs where everyone could take a quick glance and spot obvious rendering errors. If you follow AsciiDoc's mailing list [1], we'll go through a series of release candidates before the final 9.0. "With enough eyeballs, all bugs are shallow." [1]: asciidoc-discuss@xxxxxxxxxxxxxxxxxx I reply to two mailing lists; I think this particular problem belongs to asciidoc-discuss. Best regards, -- Yannick Gingras - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
