<div dir="ltr">This past year, our intern Laura Alves worked on a patch in openstack-infra/config to create docs-draft copies of HTML and PDF output. She ran out of time to get it all the way completed. Her patch is here: <a href="https://review.openstack.org/#/c/22768/">https://review.openstack.org/#/c/22768/</a><div>
<br></div><div>You could certainly use that as a starting point. </div><div><br></div><div>Thanks,</div><div>Anne</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 1, 2013 at 7:28 AM, Akihiro Motoki <span dir="ltr"><<a href="mailto:amotoki@gmail.com" target="_blank">amotoki@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I noticed I often checkout the patch and generate PDF to check their contents<br>
when I review documents (admin guide or API docs).<br>
XML is not user-friendly format to read :-(<br>
<br>
How about generating PDF (or HTML) document from the patch in Jenkins job<br>
and create a link in gate results? I believe it really helps reviewers<br>
to check content changes.<br>
<br>
It takes some more disk volumes but I think it is much smaller than<br>
volumes of devstack tempest logs so it doesn't matter.<br>
<br>
Thanks,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Akihiro MOTOKI <<a href="mailto:amotoki@gmail.com">amotoki@gmail.com</a>><br>
<br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</div>