On 2017-08-03 12:43:04 +1000 (+1000), Tony Breeds wrote: [...] > I wonder if we should look at publishing the upper-constraints.txt file > somewhere (other than cgit). If we did something like: > > tarballs.o.o/constraints/$series.txt > > We wouldn't have an issue when we EOL a branch and the url's hard-coded > in tox.ini breaking. queens.txt wouldn't exist until we branch > requirements but we could work around that with a redirect if needed. > > Later we could get really crazy and make a version that took a package > name and version perhaps like: > > tarballs.o.o/constraints/$(python setup.py --name)/$(python setup.py > --version) > > Which would redirect to the appropriate series file. I think we have > enough data in openstack/releases to generate those redirects. We'd > need to think about projects / repos that don't use the release > infrastructure. [...]
Seems like a fine enough plan, but maybe the releases site is a better place to publish these in that case? -- Jeremy Stanley
signature.asc
Description: Digital signature
__________________________________________________________________________ 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
