[openstack-dev] oslo library version summary

Matt Joyce matt.joyce at cloudscaling.com
Sun Dec 16 09:12:29 UTC 2012

So from my understanding we're using pypi as the defacto source for client

a) true?

b) should this be on pypi as well if it's similar to clients?

On Sun, Dec 16, 2012 at 12:02 AM, Monty Taylor <mordred at inaugust.com> 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.
> Thanks!
> Monty
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121216/c3061bbd/attachment.html>

More information about the OpenStack-dev mailing list