<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body dir="auto">
<div></div>
<div>FYI,</div>
<div><br>
</div>
<div>A similar discussion was held for an api-ref change in Glance:</div>
<div><a href="https://review.openstack.org/#/c/356693/">https://review.openstack.org/#/c/356693/</a></div>
<div><br>
On Sep 6, 2016, at 6:39 AM, Andreas Jaeger <<a href="mailto:aj@suse.com">aj@suse.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>On 2016-09-06 15:30, Ihar Hrachyshka wrote:</span><br>
<blockquote type="cite"><span>Andreas Jaeger <<a href="mailto:aj@suse.com">aj@suse.com</a>> wrote:</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>On 2016-09-06 15:02, Ihar Hrachyshka wrote:</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite"><span>[...]</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite"><span>Since neutron-lib is branched on stable/* boundary, I feel that it would</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite"><span>be fine to keep one-to-one relationship between neutron and neutron-lib</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite"><span>api-ref branches.</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>We only publish the api-ref documents from master,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Is it a hard requirement from infra, or just the current state of</span><br>
</blockquote>
<blockquote type="cite"><span>affairs? If the latter, we could revisit the approach. If the former, of</span><br>
</blockquote>
<blockquote type="cite"><span>course we will accommodate.</span><br>
</blockquote>
<span></span><br>
<span>It's the current state of affair - and how api-ref was designed AFAIK:</span><br>
<span>To have one tree,</span><br>
<span></span><br>
<span>Andreas</span><br>
<span>-- </span><br>
<span>Andreas Jaeger aj@{<a href="http://suse.com">suse.com</a>,<a href="http://opensuse.org">opensuse.org</a>} Twitter: jaegerandi</span><br>
<span> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany</span><br>
<span> GF: Felix Imendörffer, Jane Smithard, Graham Norton,</span><br>
<span> HRB 21284 (AG Nürnberg)</span><br>
<span> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126</span><br>
<span></span><br>
<span></span><br>
<span>__________________________________________________________________________</span><br>
<span>OpenStack Development Mailing List (not for usage questions)</span><br>
<span>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</span><br>
<span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br>
</div>
</blockquote>
</body>
</html>