Switch to semantic versioning

Discussed here:

  http://lists.openstack.org/pipermail/openstack-dev/2013-March/006283.html

The date based 2013.1 version is likely to be disallowed by PEP426
when it is ratified and we'll be required to treat the date based
version as a "private version" and use 0.2013.1 as the official
version.

Also, I'm coming around to the idea of using semantic versioning
(i.e. x.y.z) and increasing the major number when removing any
deprecated APIs. Th is the trend that Python is following according to
a discussion on distutils-sig.

One consequence of using semantic versioning is that we'll be very
loathe to remove any deprecated APIs since it will mean a version bump
from 1.y.z to 2.y.z. That's probably not a bad thing.

With this versioning scheme, I figure we should start with 1.1.0
(2013.1-2012). We'll increase the micro number when we do release from
the stable branch and increase the minor number with every coordinated
OpenStack release.

Change-Id: Ibe033d37742b82dee5f42d9e3d6a0b51582bd3ce

1 files changed, 1 insertions, 1 deletions

diff --git a/setup.py b/setup.py
index 02f9cae..a4ef33f 100644
--- a/setup.py
+++ b/setup.py
@@ -20,7 +20,7 @@ import setuptools
 from magic.openstack.common import setup
 
 package = 'oslo-config'
-version = '2013.1'
+version = '1.1.0'
 
 requires = setup.parse_requirements()
 depend_links = setup.parse_dependency_links()