<div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 22, 2014 at 4:45 PM, Joe Gordon <span dir="ltr"><<a href="mailto:joe.gordon0@gmail.com" target="_blank">joe.gordon0@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">
<div class="im">On Wed, Jan 22, 2014 at 5:19 AM, Julien Danjou <span dir="ltr"><<a href="mailto:julien@danjou.info" target="_blank">julien@danjou.info</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>On Tue, Jan 21 2014, Joe Gordon wrote:<br>
<br>
> I would like to propose having a integration test job in Oslo incubator<br>
> that syncs in the code, similar to how we do global requirements.<br>
<br>
</div>I don't think that would be possible as a voting job, since the point of<br>
oslo-incubator is to be able to break the API compatibility.<br></blockquote><div><br></div></div><div>If oslo-incubator can break APIs whenever it wants how can a downstream project stay in sync with oslo-incubator?</div>
</div></div></div></blockquote><div><br></div><div><div class="gmail_default"><span style="font-size:small">"</span>Usually the API maintainer or those making significant changes to an API take responsibility for syncing that specific module into the projects which use it" [1]</div>
<div class="gmail_default"><br></div><div class="gmail_default">[1] <a href="https://wiki.openstack.org/wiki/Oslo#Syncing_Code_from_Incubator">https://wiki.openstack.org/wiki/Oslo#Syncing_Code_from_Incubator</a><br></div>
<div class="gmail_default"><br></div><div class="gmail_default">That happens, AFAICT, when a known incompatibility is introduced. It does not always happen when a compatible change is made. I'm really not sure of the best way to improve that, other than to remind contributors to oslo of the expectations.</div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Doug</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im"><div>

 </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span><font color="#888888"><br>
--<br>
Julien Danjou<br>
;; Free Software hacker ; independent consultant<br>
;; <a href="http://julien.danjou.info" target="_blank">http://julien.danjou.info</a><br>
</font></span></blockquote></div></div><br></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>