Open Stack

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)

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.

(we might be splitting hairs on this one)

On 11/30/2012 11:07 AM, Joshua Harlow wrote:
> Is there a versioning scheme that can be followed here?
> 
> Stable releases on pypi have even numbers, odd numbers are unstable?
> 
> Isn't something like that pretty common (?), then u can just upload
> everything to pypi.
> 
> Maybe that¹s another idea.
> 
> On 11/30/12 5:45 AM, "Mark McLoughlin" <markmc at redhat.com> wrote:
> 
>> On Mon, 2012-11-26 at 22:40 +0000, Mark McLoughlin wrote:
>>> On Fri, 2012-11-23 at 11:55 +0100, Thierry Carrez wrote:
>>>> There seem to be two options there: just push everything on the same
>>>> PyPI module, or have multiple PyPI modules for each series. I'd say
>>>> the latter looks worse.
>>>
>>> I don't really buy that unstable development releases of Oslo have to go
>>> to PyPI in order for core projects to be able to consume them.
>>>
>>> pip supports http:// URLs of tarballs. Why not use that during
>>> development?
>>
>> I'm kinda waiting for opinions on this :-)
>>
>> Cheers,
>> Mark.
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>