<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 30 September 2015 at 16:02, Cathy Zhang <span dir="ltr"><<a href="mailto:Cathy.H.Zhang@huawei.com" target="_blank">Cathy.H.Zhang@huawei.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Hi Kyle,<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Is this only about the sub-projects that are ready for release? I do not see networking-sfc sub-project in the list. Does this mean we have done the pypi registrations for the networking-sfc project correctly or it is not checked because
it is not ready for release yet?</p></div></div></blockquote><div><br></div><div>Can't speak for Kyle, but with these many meaty patches in flight [1], I think it's fair to assume that although the mechanisms are in place, Kyle is not going to release the project at this time; networking-sfc release is independent, we can publish the project when the time is ripe.</div><div><br></div><div>Cheers,</div><div>Armando </div><div><br></div><div>[1] <a href="https://review.openstack.org/#/q/status:open+project:openstack/networking-sfc,n,z">https://review.openstack.org/#/q/status:open+project:openstack/networking-sfc,n,z</a> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
<p class="MsoNormal">Cathy<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<div style="border-style:solid none none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"> Kyle Mestery [mailto:<a href="mailto:mestery@mestery.com" target="_blank">mestery@mestery.com</a>]
<br>
<b>Sent:</b> Wednesday, September 30, 2015 11:55 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> [openstack-dev] [neutron] pypi packages for networking sub-projects<u></u><u></u></span></p>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt">Folks:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt">In trying to release some networking sub-projects recently, I ran into an issue [1] where I couldn't release some projects due to them not being registered on pypi. I have a patch out [2] which adds pypi publishing
jobs, but before that can merge, we need to make sure all projects have pypi registrations in place. The following networking sub-projects do NOT have pypi registrations in place and need them created following the guidelines here [3]:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">networking-calico<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">networking-infoblox<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">networking-powervm<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt">The following pypi registrations did not follow directions to enable openstackci has "Owner" permissions, which allow for the publishing of packages to pypi:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">networking-ale-omniswitch<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">networking-arista<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">networking-l2gw<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">networking-vsphere<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><br>
Once these are corrected, we can merge [2] which will then allow the neutron-release team the ability to release pypi packages for those packages.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks!<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Kyle<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br>
[1] <a href="http://lists.openstack.org/pipermail/openstack-infra/2015-September/003244.html" target="_blank">
http://lists.openstack.org/pipermail/openstack-infra/2015-September/003244.html</a><br>
[2] <a href="https://review.openstack.org/#/c/229564/1" target="_blank">https://review.openstack.org/#/c/229564/1</a><br>
[3] <a href="http://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases" target="_blank">
http://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases</a><u></u><u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>
<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>
<br></blockquote></div><br></div></div>