Open Stack

On 11/26/2012 06:38 AM, Doug Hellmann wrote:

>     I can picture one option where we would version oslo libraries
>     separately, based on classic major.minor.patch format. We could make
>     "stable branches" based off major versions. That would be separate from
>     the common development cycles and milestones, even if for planning (and
>     summit) reasons you would still talk about "grizzly development
>     timeframe", and try to slow down towards the end of the cycle. We can
>     push all versions to PyPI and use ">=1.2.1 <2" style to solve the
>     dependency specification... and push to Launchpad in parallel to provide
>     a sane, series-oriented view of the same deliverables.
>
>     How does that sound ?

I agree with this. I am not worried about presenting multiple 
'potentially confusing' versions of the oslo libraries on PyPI in the 
same way I am with client libraries, so I think this will work just fine.

BTW - how's that upload-to-pypi jenkins job builder template coming 
along? :)

Monty