Use revno and git sha for pre-release versioning.

In discussions with ttx and zul, it became clear that the git describe info
for our intra-release case wasn't providing any value and was providing
confusion. Additionally, plain git sha's are not providing enough info.

So, the scheme settled on that breaks the least amount of things and yet
still reduces complexity is:

if pre-version: # server projects
  try:
    use current tag
  except:
    use pre-version+revcount+gitsha
else:
  use git describe | s/-/./

Additionally, we'll use a as a prefix for the revcount, b as the prefix for
the milestone portion of a milestone tag, and rc as the prefix for rc's, so
that for our releases, python version sorting works as expected.

Change-Id: I6f0fe029d225afa8f435bc83216fc144c2402ae0

1 files changed, 1 insertions, 1 deletions

diff --git a/setup.py b/setup.py
index 0a590a1..9262a09 100644
--- a/setup.py
+++ b/setup.py
@@ -42,7 +42,7 @@ weights = [
 
 setuptools.setup(
     name=package,
-    version=setup.get_version(package),
+    version=setup.get_version(package, '2013.1'),
     description="Common components for Openstack",
     long_description="Common components for Openstack "
                      "including paster templates.",