Hey Kyle, I have updated the ownership of networking-l2gw. I have +1'd your patch. As soon as it merges the ACLs for the L2GW project will be fine as well. Thanks for confirming about the networking-arista. With this both of these packages should be good to go. Thanks -Sukhdev On Wed, Sep 30, 2015 at 11:55 AM, Kyle Mestery <mestery at mestery.com> wrote: > Folks: > > 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]: > > networking-calico > networking-infoblox > networking-powervm > > The following pypi registrations did not follow directions to enable > openstackci has "Owner" permissions, which allow for the publishing of > packages to pypi: > > networking-ale-omniswitch > networking-arista > networking-l2gw > networking-vsphere > > 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. > > Thanks! > Kyle > > [1] > http://lists.openstack.org/pipermail/openstack-infra/2015-September/003244.html > [2] https://review.openstack.org/#/c/229564/1 > [3] > http://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150930/24313cf4/attachment.html>