On Thu, Oct 15, 2015 at 7:03 AM, Neil Jerram
wrote:
> On 02/10/15 12:33, Neil Jerram wrote:
> > On 02/10/15 11:42, Neil Jerram wrote:
> >> Thanks Kyle! I'm looking at this now for networking-calico.
> > Done, please see https://pypi.python.org/pypi/networking-calico.
> >
> > When you release, how
On 02/10/15 12:33, Neil Jerram wrote:
> On 02/10/15 11:42, Neil Jerram wrote:
>> Thanks Kyle! I'm looking at this now for networking-calico.
> Done, please see https://pypi.python.org/pypi/networking-calico.
>
> When you release, how will the version number be decided? [...]
Excitingly, I believe
On 02/10/15 16:03, Jeremy Stanley wrote:
> On 2015-10-02 11:33:05 + (+), Neil Jerram wrote:
> [...]
>> For the PyPI registration I put 0.1.0, but that doesn't mean that I
>> expect that to be the version number when networking-calico is actually
>> released. I guessed that PyPI might impose
On 2015-10-02 11:33:05 + (+), Neil Jerram wrote:
[...]
> For the PyPI registration I put 0.1.0, but that doesn't mean that I
> expect that to be the version number when networking-calico is actually
> released. I guessed that PyPI might impose an increasing version number
> requirement, and
On Fri, Oct 2, 2015 at 6:33 AM, Neil Jerram
wrote:
> On 02/10/15 11:42, Neil Jerram wrote:
> > Thanks Kyle! I'm looking at this now for networking-calico.
>
> Done, please see https://pypi.python.org/pypi/networking-calico.
>
> When you release, how will the version number be decided? And should
On 02/10/15 11:42, Neil Jerram wrote:
> Thanks Kyle! I'm looking at this now for networking-calico.
Done, please see https://pypi.python.org/pypi/networking-calico.
When you release, how will the version number be decided? And should I
make a change to put that version into the source somewhere,
On 30/09/15 19:58, Kyle Mestery 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
: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] pypi packages for networking sub-projects
On Wed, Sep 30, 2015 at 8:26 PM, Armando M.
mailto:arma...@gmail.com>> wrote:
On 30 September 2015 at 16:02, Cathy Zhang
mailto:cathy.h.zh...@huaw
g-sfc,n,z
>
>
>>
>>
>> Thanks,
>>
>> Cathy
>>
>>
>>
>> *From:* Kyle Mestery [mailto:mest...@mestery.com]
>> *Sent:* Wednesday, September 30, 2015 11:55 AM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>>
t; *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 re
From: Kyle Mestery [mailto:mest...@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
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,
Sukhdev, you're right, for some reason that one didn't show up in a pypi
search on pypi itself, but does in google. And it is correctly owned [1].
[1] https://pypi.python.org/pypi/networking_arista
On Wed, Sep 30, 2015 at 2:21 PM, Sukhdev Kapur
wrote:
> Hey Kyle,
>
> I am bit confused by this.
Kyle,
I have taken care of this for networking-infoblox. Please let me know if
anything else is necessary.
Thanks,
John
On Sep 30, 2015, at 2:55 PM, Kyle Mestery
mailto:mest...@mestery.com>> wrote:
Folks:
In trying to release some networking sub-projects recently, I ran into an issue
[1] wh
Hey Kyle,
I am bit confused by this. I just checked networking-arista and see that
the co-owner of the project is openstackci
I also checked the [1] and [2] and the settings for networking-arista are
correct as well.
What else is missing which make you put networking-arista in the second
category
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
16 matches
Mail list logo
