[openstack-dev] [requirements] separating the code and data in openstack/requirements
Robert Collins
robertc at robertcollins.net
Tue Jul 7 23:36:46 UTC 2015
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
-Rob
--
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud
More information about the OpenStack-dev
mailing list