Hi Galo,
I think the goal of this split is well explained by Sandro in the first
mails of the chain:
1. Downstream packaging
2. Tagging the delivery properly as a library
3. Adding as a project on pypi
OpenStack provide us a tarballs web page[1] for each branch of each
project of the infrastructure.
Then, projects like Delorean can allow us to download theses tarball master
branches, create the
packages and host them in a target repository for each one of the rpm-like
distributions[2]. I am pretty sure
that there is something similar for Ubuntu.
Everything is done in a very straightforward and standarized way, because
every repo has its own
deliverable. You can look how they are packaged and you won't see too many
differences between
them. Packaging a python-midonetclient it will be trivial if it is
separated in a single repo. It will be
complicated and we'll have to do tricky things if it is a directory inside
the midonet repo. And I am not
sure if Ubuntu and RDO community will allow us to have weird packaging
metadata repos.
So to me the main reason is
4. Leverage all the infrastructure and procedures that OpenStack offers to
integrate MidoNet
as best as possible with the release process and delivery.
Regards,
[1]: http://tarballs.openstack.org/
[2]: http://trunk.rdoproject.org
On 9 December 2015 at 15:52, Antoni Segura Puimedon <t...@midokura.com>
wrote:
>
> ---------- Forwarded message ----------
> From: Galo Navarro <g...@midokura.com>
> Date: Wed, Dec 9, 2015 at 2:48 PM
> Subject: Re: [openstack-dev] [midonet] Split up python-midonetclient
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Cc: Jaume Devesa <ja...@midokura.com>
>
>
> >> Ditto. We already have a mirror repo of pyc for this purpose
> >> https://github.com/midonet/python-midonetclient, synced daily.
> >
> > Some of the problems with that is that it does not have any git log
> history
> > nor does it feel like a coding project at all.
>
> Of course, because the goal of this repo is not to provide a
> changelog. It's to provide an independent repo. If you want git log,
> you should do a git log python-midonetclient in the source repo
> (/midonet/midonet).
>
> > Allow me to put forward a solution that will allow you keep the
> development
> > in the midonet tree while, at the same time, having a proper repository
> > with identifiable patches in github.com/midonet/python-midonetclient
>
> Thanks, but I insist: can we please clarify *what* are we trying to
> achieve, before we jump into solutions?
>
> g
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Jaume Devesa
Software Engineer at Midokura
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
