Open Stack

Monty Taylor wrote:
> Actually, if we have some snapshot releases which look like this:
> 2012.2~G2~5 (for instance)
> 
> That get turned in to python versions that look like this:
> 2012.2-alpha2.5  (for instance)

Yes, that was one of the options I considered, translating into
something that PyPI actually supports. I tried to avoid that because it
makes us use two different-looking version numbers to represent the same
thing (2013.1~G2 = 2013.2-alpha2), but since for oslo libraries we'll
have to push intermediary versions between milestones anyway... it's no
longer a 1:1 match. So I guess it's not such a big deal.

> Then I don't understand why we couldn't upload snapshots and real
> releases to pypi - and then have nova do:
> oslo-foo>=2012.2,<=2013.1
> In its pip-requires.

That's what I proposed higher in the thread, but Mark replied:

> I really, really hate version caps like that :)

So I suspect there is no consensus yet about that...

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack