[openstack-dev] [neutron] pypi packages for networking sub-projects
Armando M.
armamig at gmail.com
Thu Oct 1 01:26:50 UTC 2015
On 30 September 2015 at 16:02, Cathy Zhang <Cathy.H.Zhang at huawei.com> wrote:
> Hi Kyle,
>
>
>
> 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?
>
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.
Cheers,
Armando
[1]
https://review.openstack.org/#/q/status:open+project:openstack/networking-sfc,n,z
>
>
> Thanks,
>
> Cathy
>
>
>
> *From:* Kyle Mestery [mailto:mestery at mestery.com]
> *Sent:* Wednesday, September 30, 2015 11:55 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [neutron] pypi packages for networking
> sub-projects
>
>
>
> 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/c4208abc/attachment.html>
More information about the OpenStack-dev
mailing list