Open Stack

On Tue, Dec 8, 2015 at 3:31 PM, Sandro Mathys <sandro at midokura.com> wrote:
> Hi,
>
> As Takashi Yamamoto raised in another thread [0], python-midonetclient
> should be split out into its own repo. There's two major reasons for
> this:
>
> 1) (Downstream) packaging: midonet and python-midonetclient are two
> distinct packages, and therefore should have distinct upstream
> tarballs - which are compiled on a per repo basis.
>
> 2) When adding repositories to OpenStack, they need to be tagged.
> There's a bunch of tags, and one category is the "type": library [1]
> or service [2]. Now midonet is a service, but python-midonetclient is
> a library so they need to be separate repositories.
>

3) In order to put python-midonetclient on PyPI, it's probably
required to be in its own repo as well, isn't it? Because that's
another requirement [3]

> Thoughts?
>
> Cheers,
> Sandro
>
> [0] http://lists.openstack.org/pipermail/openstack-dev/2015-December/081216.html
> [1] http://governance.openstack.org/reference/tags/type_library.html
> [2] http://governance.openstack.org/reference/tags/type_service.html
[3] http://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases