[Openstack] proposal for policy around and management of client libraries

Dolph Mathews dolph.mathews at gmail.com
Mon Nov 7 22:49:52 UTC 2011


Because it should be keystone's responsibility to test it's constant stream
of API changes, and abstract that away from it's consumers.

On Mon, Nov 7, 2011 at 3:25 PM, Caitlin Bestler <Caitlin.Bestler at nexenta.com
> wrote:

> Monty Taylor wrote:
>
> > OpenStack projects that need to depend on these will reference the git
> repo of the project in their
> > tools/pip-requires file. This should take care of depends for
> developers. Normal installation depends
> > can be taken care of by distro packagers as usual.
>
> Why would an openstack project *need* to reference a client library of
> another openstack project?
>
> Wouldn't requiring openstack projects to rely on the REST API of other
> projects eliminate a whole mess
> of release dependencies?
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20111107/b7059981/attachment.html>


More information about the Openstack mailing list