<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 23 November 2016 at 16:42, Joshua Harlow <span dir="ltr"><<a href="mailto:harlowja@fastmail.com" target="_blank">harlowja@fastmail.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">A suggestion would also to setup something like the following:<br>
<br>
<a href="https://wiki.openstack.org/wiki/Oslo#Periodic" rel="noreferrer" target="_blank">https://wiki.openstack.org/wik<wbr>i/Oslo#Periodic</a><br>
<br>
Get the users of neutron lib being tested against the latest neutron lib (at least nightly) and seeing if they will be borked by a new neutron lib merge...<br>
<br>
<a href="http://status.openstack.org/openstack-health/#/?groupKey=build_name&resolutionKey=hour&searchProject=-with-oslo" rel="noreferrer" target="_blank">http://status.openstack.org/op<wbr>enstack-health/#/?groupKey=bui<wbr>ld_name&resolutionKey=hour&sea<wbr>rchProject=-with-oslo</a><br>
<br>
Overall be careful with the APIs u expose and plan out how u will shift users from the old API to the new API (without destroying the world during that transition).<br>
<br>
My 3 cents :-P<br></blockquote><div><br></div><div>I take the 3 cents, but we already do that :)</div><div> </div><div><a href="http://status.openstack.org/openstack-health/#/?groupKey=build_name&resolutionKey=hour&searchProject=-with-neutron-lib-master">http://status.openstack.org/openstack-health/#/?groupKey=build_name&resolutionKey=hour&searchProject=-with-neutron-lib-master</a><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-Josh<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
Boden Russell wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I would encourage anyone working on neutron-lib related changes to have<br>
a peek at the recently renovated contributing doc [1] if you haven't<br>
already.<br>
<br>
In particular the 'Phase 4: Consume' section [2] provides some tips on<br>
how we see this workflow playing out.<br>
<br>
Thanks<br>
<br>
[1]<br>
<a href="https://github.com/openstack/neutron-lib/blob/master/doc/source/contributing.rst" rel="noreferrer" target="_blank">https://github.com/openstack/n<wbr>eutron-lib/blob/master/doc/sou<wbr>rce/contributing.rst</a><br>
[2]<br>
<a href="https://github.com/openstack/neutron-lib/blob/master/doc/source/contributing.rst#phase-4-consume" rel="noreferrer" target="_blank">https://github.com/openstack/n<wbr>eutron-lib/blob/master/doc/sou<wbr>rce/contributing.rst#phase-4-<wbr>consume</a><br>
<br>
<br>
On 11/23/16 12:39 PM, Armando M. wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi neutrinos,<br>
<br>
In the last few hours a couple of changes landed [1,2] that caused a bit<br>
of a jam in the neutron subproject gates, as they overlapped with<br>
another change [3] having impact on the subprojects.<br>
<br>
This is why it is important to communicate during team meetings and/or<br>
ML that patches with potential impact are in flight in our review<br>
pipeline, so that we do our best to coordinate the merge process without<br>
shooting ourselves in the foot.<br>
<br>
To bring this back to sanity, I issued a temporary revert [4], so that<br>
[5] can land undisturbed. After that, a double revert will be applied,<br>
once subprojects have had the opportunity to deal with the aftermath of<br>
the other breaking change [1,2] (e.g. [6,7]).<br>
<br>
 From now on, I'd strongly encourage people proposing/reviewing patches<br>
with potential impact (any impact) to err on the side of caution, and<br>
take the advised steps to ensure such situations don't happen in the future.<br>
<br>
Thanks,<br>
Armando<br>
<br>
[1] <a href="https://review.openstack.org/#/c/397704/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/397704/</a><br>
[2] <a href="https://review.openstack.org/#/c/397037/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/397037/</a><br>
[3] <a href="https://review.openstack.org/#/c/386845/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/386845/</a><br>
[4] <a href="https://review.openstack.org/#/c/401377/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/401377/</a><br>
[5] <a href="https://review.openstack.org/#/q/topic:plugin-directory+status:open" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/q/topic:plugin-directory+stat<wbr>us:open</a><br>
[6] <a href="https://review.openstack.org/#/c/401263/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/401263/</a><br>
[7] <a href="https://review.openstack.org/#/c/401355/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/401355/</a><br>
<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>
<br>
</blockquote>
<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>
</blockquote>
<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></div><br></div></div>