<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Kyle,
<div class=""><br class="">
</div>
<div class="">I have taken care of this for networking-infoblox. Please let me know if anything else is necessary.</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class="">John</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Sep 30, 2015, at 2:55 PM, Kyle Mestery <<a href="mailto:mestery@mestery.com" class="">mestery@mestery.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">
<div class="">Folks:<br class="">
<br class="">
</div>
<div class="">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]:<br class="">
<br class="">
</div>
<div class="">networking-calico<br class="">
</div>
<div class="">networking-infoblox<br class="">
</div>
<div class="">networking-powervm<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">The following pypi registrations did not follow directions to enable openstackci has "Owner" permissions, which allow for the publishing of packages to pypi:<br class="">
<br class="">
</div>
<div class=""></div>
<div class="">networking-ale-omniswitch<br class="">
</div>
<div class="">networking-arista<br class="">
</div>
<div class="">networking-l2gw<br class="">
</div>
<div class="">networking-vsphere<br class="">
</div>
<div class=""><br class="">
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.<br class="">
<br class="">
</div>
<div class="">Thanks!<br class="">
</div>
<div class="">Kyle<br class="">
</div>
<div class=""><br class="">
[1] <a href="http://lists.openstack.org/pipermail/openstack-infra/2015-September/003244.html" class="">
http://lists.openstack.org/pipermail/openstack-infra/2015-September/003244.html</a><br class="">
[2] <a href="https://review.openstack.org/#/c/229564/1" class="">https://review.openstack.org/#/c/229564/1</a><br class="">
[3] <a href="http://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases" class="">
http://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases</a><br class="">
</div>
</div>
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>