Comment 4 for bug 1206730

>
> Milestone version is a beta and is from the milestone-proposed branch.

milestone-proposed branch? There are no branches involved here, only
tags.

We are doing continuous deployment. We have jenkins build an RPM after
each commit to upstream master. We use the output of python setup.py
--version as the version of the RPM.

In the example I gave in the bug description jenkins produced
glance-2013.2.a115.gd675456.rpm and then we installed and tested it in
our integration environment. jenkins ran again a few hours later
because of more upstream commits and produced
glance-2013.2.a2.gadb454d.rpm. When we did "yum install
glance-2013.2.a2.gadb454d" it failed because yum refused to downgrade
(this is arguably an issue with yum: it refuses to install a version it
thinks is older than the currently installed version).

So, our options are to change pbr so that newer commits to master always
have setup.py --version output a version that is greater or version our
rpms using an alternative method.