<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 16, 2013 at 2:40 PM, Andreas Jaeger <span dir="ltr"><<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 08/16/2013 09:07 PM, Anne Gentle wrote:<br>
> Hi all,<br>
> You may have noticed there has been a lot of discussion in reviews<br>
> around the validation gate for openstack-manuals. Or perhaps you didn't<br>
> notice, and that's why I'm talking about this on the list. I also need<br>
> to straighten it out in my own mind. Writing helps. :)<br>
><br>
> I like the idea of categories of gating jobs. Some are voting, which<br>
> means your patch will get a red X mark. Some are non-voting, which means<br>
> your patch will get an informative message telling you some of your<br>
> submission isn't right.<br>
><br>
> So I want to sort out what we want to test on new submissions:<br>
><br>
> This is the most important one: Do all the books build? If not which<br>
> ones are problematic and why? Ideally the gate test will build only the<br>
> books that have changed files. Is this happening now?<br>
<br>
</div>AFAIK all books build - and the gate test only builds those books that<br>
have changed files. Still, this needed a couple of iterations to get<br>
right, so everybody should double check that there are no further bugs<br>
in it.<br>
<div class="im"><br></div></blockquote><div><br></div><div>This is looking good and caught a missing xi:include for me while working on moving content into the Configuration Reference. Greatly appreciated!</div><div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> This is less important to me: Are we being careful about whitespace? If<br>
> not which ones are failing the whitespace tests?<br>
><br>
> And this one is problematic: Do individual files validate? With xrefs in<br>
> the source file, the files will not validate in Oxygen. To me,<br>
> validation can be non-voting as long as the books build.<br>
<br>
<br>
> We can use 1.9.0 (or 1.9.2 when it's released) in the pom.xml but also<br>
> the xlink markup would have to be changed. This isn't an<br>
> overnight-flip-the-switch kind of change. We need to talk about<br>
> policies. Let's have that discussion at the boot camp.<br>
<br>
</div>Please write this up for those that won't be there.<br></blockquote><div><br></div><div>Yep, will do. We're documentors! :)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> Also, we need the "Failed" messages about images to be fixed in the<br>
> build tool in order to make these logs more useful. David, definitely<br>
> move this bug up on your priority<br>
> list. <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1193491" target="_blank">https://bugs.launchpad.net/openstack-manuals/+bug/1193491</a><br>
<br>
</div>Indeed, it produces lots of noise.<br>
<div class="im"><br>
> In the meantime, let's make sure whitespace remains non-voting.<br>
<br>
</div>There's a patch from Tom that needs approval:<br>
<a href="https://review.openstack.org/#/c/41623/" target="_blank">https://review.openstack.org/#/c/41623/</a><br>
<br>
Also, I suggest to get this one in - to produce less whitespace:<br>
<a href="https://review.openstack.org/#/c/41627/" target="_blank">https://review.openstack.org/#/c/41627/</a><br>
<div class="im"><br></div></blockquote><div><br></div><div>Both are in now and we're only gating on "does it build?" </div><div><br></div><div>Thanks for the good work!</div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">
> Any questions? I don't know if I clarified much but I wanted to ensure<br>
> you know I'm paying attention and doing what I can to mitigate any<br>
> difficulties getting good content through the gate.<br>
<br>
</div>I think we're on a good way forward.<br>
<br>
Thanks,<br>
Andreas<br>
<span class="HOEnZb"><font color="#888888">--<br>
Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica: jaegerandi<br>
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br>
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<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></div>