openstack.common.setup has functions to determine the current version of a project state. These functions work in two cases (other configurations return a default version of 0.0.0). Versioning works if you run setup.py within the git repository of a project or if project/versioninfo is available relative to setup.py.
Running setup.py within the git repository generates a versioninfo file at project/versioninfo. Knowing this, the correct way to build an sdist for a project is to run `python setup.py sdist` within the git repository and have setup.py include project/versioninfo as part of the package data. If you don't include the versioninfo file as part of the package data the sdist package will report its version as 0.0.0.
To add versioninfo as package data add it as an include in the project's MANIFEST.in. For example:
include glance/versioninfo
The commit at the head of glance's master branch does not currently do this. As a result glance sdist builds report their version to be 0.0.0.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit eb8c956753fb7b3
Author: Clark Boylan <email address hidden>
Date: Wed Aug 22 17:04:23 2012 -0700
Add glance/versioninfo to MANIFEST.in.
Fixes bug #1040734
Adding glance/versioninfo to MANIFEST.in adds the versioninfo file to
sdist packages. Adding this file to sdist packages allows versioning to
work properly when installing from an sdist package.
Change-Id: I7c9d2843e428fb