[openstack-dev] When will we stop adding new Python modules to requirements
Michael Basnight
mbasnight at gmail.com
Mon Sep 16 15:36:05 UTC 2013
On Sep 16, 2013, at 12:24 AM, Matthias Runge <mrunge at redhat.com> wrote:
> On 16/09/13 05:30, Monty Taylor wrote:
>>
>>
>> On 09/15/2013 01:47 PM, Alex Gaynor wrote:
>>> Falcon was included as a result of Marconi moving from stackforge to
>>> being incubated. sphinxcontrib-programoutput doesn't appear to have been
>>> added at all, it's still under
>>> review: https://review.openstack.org/#/c/46325/
>>
>> I agree with Alex and Morgan. falcon was the marconi thing.
>> diskimage-builder and tripleo-image-elements are part of an OpenStack
>> program.
>>
>> sphinxcontrib-programoutput is only a build depend for docs - but I
>> think you're made a good point, and we should be in requirements freeze.
>> Let's hold off on that one until icehouse opens.
>
>
> Not to forget python-troveclient, which is currently a hard requirement
> for Horizon.
>
> During the review for python-troveclient, it was discovered, troveclient
> still references reddwarfclient (in docs/source).
Are you saying it references another codebase? Or just that when we renamed it we forgot to update a reference or two? If its the latter, is it relevant to this requirements issue? Also, I will gladly fix it and release it if its making anyone's life hell :)
More information about the OpenStack-dev
mailing list