<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 22 June 2017 at 14:01, Dougal Matthews <span dir="ltr"><<a href="mailto:dougal@redhat.com" target="_blank">dougal@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="gmail-">On 22 June 2017 at 11:01, Thierry Carrez <span dir="ltr"><<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>Thierry Carrez wrote:<br>
> Renat Akhmerov wrote:<br>
>> We have a weekly meeting next Monday, will it be too late?<br>
><br>
> Before Thursday EOD (when the Pike-2 deadline hits) should be OK.<br>
<br>
</span>If there was a decision, I missed it (and in the mean time Mistral<br>
published 5.0.0.0b2 for the Pike-2 milestone).<br>
<br>
Given the situation, I'm fine with giving an exception to Mistral to<br>
switch now to cycle-with-intermediary and release 5.0.0 if you think<br>
master is currently releasable...<br>
<br>
Let me know what you think.<br></blockquote><div><br><br></div></span><div>I think that probably is the best option.<br><br></div><div>We have been trying to break the requirement on mistral (from tripleo-common) but it is proving to be harder than expected. We are really doing some nasty things, but I wont go into details here :-) If anyone is interested, feel free to reach out.<br></div></div></div></div></blockquote><div><br></div><div>After sending that we did make some solid progress. We are two patches away from breaking the link AFAICT.<br></div><div><br>1. <a href="https://review.openstack.org/#/c/454719/">https://review.openstack.org/#/c/454719/</a><br>2. <a href="https://review.openstack.org/#/c/476866/">https://review.openstack.org/#/c/476866/</a><br><br></div><div>Both have some errors that need to be resolved but it is looking much closer now.<br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><span class="gmail-"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="gmail-m_5939002815520772258HOEnZb"><div class="gmail-m_5939002815520772258h5"><br>
--<br>
Thierry Carrez (ttx)<br>
<br>
______________________________<wbr>______________________________<wbr>______________<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.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></span></div><br></div></div>
</blockquote></div><br></div></div>