On Sun, 2015-08-30 at 12:49 +0000, Jeremy Stanley wrote: > On 2015-08-30 10:23:32 +0200 (+0200), Thomas Bechtold wrote: > [...] > > Maybe the tarball won't be regenerated if only a new git tag is > > pushed? > > In that case the latest commit-id doesn't change but the content of > > the > > tarball need to change (from 3.2.1.dev24 to 3.3.0). > > Correct, nobody has implemented a mechanism for our tarball jobs to > identify which branch tips need regenerating when a tag is pushed, > so the version numbers embedded within them will lag (potentially > for long periods if those branches don't see much new activity).
Can you point me to the code where this needs to be implemented? > An > alternative is to generate your own tarballs from the git repo with > `tox -e venv python setup.py sdist` and consume the result from the > dist subdirectory. Yeah. But then the whole tarballs.openstack.org thingy is imo somehow useless... Cheers, Tom __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
