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