<div dir="ltr">Ihar, Mark thank you for your comments!<div><br></div><div>Change [1] is ready, so we can land it in Neutron. For subprojects it will be up to them to have HEAD files or not - tests won't fail, just warning message will be shown.</div><div><br></div><div>[1] - <a href="https://review.openstack.org/#/c/232607" target="_blank">https://review.openstack.org/#/c/232607</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 9, 2015 at 8:16 PM, Mark McClain <span dir="ltr"><<a href="mailto:mark@mcclain.xyz" target="_blank">mark@mcclain.xyz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span class=""><div><blockquote type="cite"><div><div><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">There are pros and cons for both approaches, but overall, I don’t see how the former justify having HEAD files and the complexity to handle them in code and in file system.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"></div></div></blockquote></div><br></span><div>The HEAD file is a clear winner when gate load is high and there are competing migrations.  As you pointed out PEP8 will detect the problem, but not fast enough to cause a ripple in the changes behind it in the gate.  The ripple causes resources to be wasted adding to the load, so the git merge conflict was the best compromise we developed.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>mark</div></font></span></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Regards,<div>Ann Kamyshnikova</div><div>Mirantis, Inc</div></div></div>
</div>