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