Open Stack

On 01/26/2013 05:00 AM, Mark McLoughlin wrote:
> On Sun, 2012-12-16 at 00:02 -0800, Monty Taylor wrote:
>> Hey all,
>>
>> ttx, markmc and I synced up on the versioning of oslo libraries, and
>> have settled on a system which is a superset of what we do with client
>> libraries - which means we can just implement an additional feature in
>> the current code and it'll handle both sets of things. We'll sync up
>> later on to discuss applicability of this to the server projects as well.
>>
>> Essentially, it breaks down like this:
>>
>> A tag to the repo will trigger tarball generation.
>>
>> If the tag contains alpha\d*, beta\d* or rc\d*, the tarball will only be
>> uploaded to tarballs.openstack.org. This will allow those pre-releases
>> to be used in the other projects.
>>
>> Otherwise, the tarball will be uploaded to tarballs.o.o AND PyPI. This
>> should allow us to use released versions of oslo libraries in pip-requires.
>>
>> Turns out it's easy to implement:
>>
>> https://review.openstack.org/#/c/18171/
>>
>> As soon as that lands, we should be able to handle the oslo requirements.
> 
> Latest oslo-config repo is here:
> 
>   http://github.com/markmc/openstack-config
> 
> and proposed for import here:
> 
>   https://review.openstack.org/20117
> 
> Given the recent versioning changes, a tarball built from this repo
> currently has 2012.3.a84.gc490e35 as its version.
> 
> I guess I shouldn't do alpha releases since that needlessly conflicts
> with the alpha versioning scheme we use for git snapshots?
> 
> So, if/when I want to release the first beta, I do:
> 
>   $> git tag -s 2012.3b1
> 
> building that gives:
> 
>   $> python setup.py sdist
>   $> ls dist/
>   oslo-config-2012.3b1.tar.gz
> 
> and pushing the tag would cause the tarball to be uploaded:
> 
>   $> git push gerrit tag 2012.3b1
> 
> and sometime in the future, Thierry or I would do:
> 
>   $> git push gerrit tag 2012.3
> 
> and that would get uploaded to PyPI.

Yup!