The issue is that since the change below - https://review.openstack.org/553045 - we are not picking up the latest neutron master code.
From: Thomas Morin <thomas.mo...@orange.com> Organization: Orange S.A. Reply-To: OpenStack List <openstack-dev@lists.openstack.org> Date: Monday, March 19, 2018 at 1:46 PM To: OpenStack List <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [requirements][neutron] Depending on pypi versions Hi Gary, See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128311.html > Note that thanks to the tox-siblings feature, we really continue to > install neutron and horizon from git - and not use the versions in > the global-requirements constraints file, I think it is worth adding a comment in (test-)requirements.txt that the OpenStack CI is overriding the version and uses git. -Thomas Gary Kotton, 2018-03-19 11:25: Hi, The change https://github.com/openstack/requirements/commit/35653e8c5044bff1059ddddf50a82b6065176eea has created some issues with decomposed neutron plugins. Let me try and give an example to explain. Say for example a patch landed in neutron master that exposed feature X. Now if a decomposed plugin wants to consume this it will fail as the decomposed plugin will pull in the latest tag. Does this mean for each new feature that we wish to consume we will need to update neutron tags? Please advise. Thanks Gary __________________________________________________________________________ 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
