[openstack-dev] [requirements] separating the code and data in openstack/requirements
Sean Dague
sean at dague.net
Wed Jul 8 10:31:48 UTC 2015
On 07/07/2015 07:36 PM, Robert Collins wrote:
> I wanted to see what folk thought about moving the requirements
> management code (update.py etc etc) to a branchless model.
>
> e.g.:
> openstack/requirements
> - global-requirements.txt
> - upper-constraints.txt
> - README.rst
> - nothing else. Not even a setup.py.
> openstack-dev/requirements-tools
> - update-constraints (aka) update.py etc etc
> - the integration tests, build-wheels.sh etc
> - everything else
I'd still stick it in openstack/
openstack-dev is an odd vestigial space, which we largely haven't
removed because there are *so* many devstack clones out there moving
devstack to openstack/ would break the world.
Otherwise sounds great.
-Sean
--
Sean Dague
http://dague.net
More information about the OpenStack-dev
mailing list