Document the TAP13 structure required for resultsdb and bodhi comment reporting
ClosedPublic

Authored by jskladan on Oct 16 2014, 10:03 AM.

Details

Summary

This is an initial version of the documentation describing the TAP13 output and its (special) structure in Taskotron.

Now is probably the time for someone with sleet-english-skillz to take over and polish the text.

Test Plan

make docs

Diff Detail

Repository
rLTRN libtaskotron
Lint
Lint Skipped
Unit
Unit Tests Skipped
jskladan retitled this revision from to Document the TAP13 structure required for resultsdb and bodhi comment reporting.Oct 16 2014, 10:03 AM
jskladan updated this object.
jskladan edited the test plan for this revision. (Show Details)
jskladan added reviewers: tflink, adamwill, kparal.
kparal added inline comments.Oct 16 2014, 10:53 AM
docs/source/tapformat.rst
13

Hyperlink for "TAP13 specification"?

33

Since the second example is also not ok, we could have ok for the first one.

42

If you want this to look like code, use double backticks. Single backtick is interpreted text:
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#interpreted-text

kparal added inline comments.Oct 16 2014, 10:55 AM
docs/source/tapformat.rst
13

/me headdesk
Of course it's mentioned in the previous paragraph.

jskladan updated this revision to Diff 709.Oct 16 2014, 10:56 AM
  • Fixed according to review
This revision is now accepted and ready to land.Oct 16 2014, 11:15 AM
jskladan closed this revision.Oct 17 2014, 9:11 AM
jskladan updated this revision to Diff 718.

Closed by commit rLTRNfff55dc614c2 (authored by @jskladan).