On Sat, Sep 6, 2014 at 8:43 AM, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > > > On 8/29/2014 1:53 PM, Kyle Mestery wrote: >> >> On Fri, Aug 29, 2014 at 1:40 PM, Matt Riedemann >> <mrie...@linux.vnet.ibm.com> wrote: >>> >>> >>> >>> On 7/29/2014 4:12 PM, Kyle Mestery wrote: >>>> >>>> >>>> On Tue, Jul 29, 2014 at 3:50 PM, Nader Lahouti <nader.laho...@gmail.com> >>>> wrote: >>>>> >>>>> >>>>> Hi Kyle, >>>>> >>>>> I have a BP listed in >>>>> https://blueprints.launchpad.net/python-neutronclient >>>>> and looks like it is targeted for 3.0 (it is needed fro juno-3) The >>>>> code >>>>> is >>>>> ready and in the review. Can it be a included for 2.3.7 release? >>>>> >>>> Yes, you can target it there. We'll see about including it in that >>>> release, pending review. >>>> >>>> Thanks! >>>> Kyle >>>> >>>>> Thanks, >>>>> Nader. >>>>> >>>>> >>>>> >>>>> On Tue, Jul 29, 2014 at 12:28 PM, Kyle Mestery <mest...@mestery.com> >>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> All: >>>>>> >>>>>> I spent some time today cleaning up python-neutronclient in LP. I >>>>>> created a 2.3 series, and created milestones for the 2.3.5 (June 26) >>>>>> and 2.3.6 (today) releases. I also targeted bugs which were released >>>>>> in those milestones to the appropriate places. My next step is to >>>>>> remove the 3.0 series, as I don't believe this is necessary anymore. >>>>>> >>>>>> One other note: I've tentatively created a 2.3.7 milestone in LP, so >>>>>> we can start targeting client bugs which merge there for the next >>>>>> client release. >>>>>> >>>>>> If you have any questions, please let me know. >>>>>> >>>>>> Thanks, >>>>>> Kyle >>>>>> >>>>>> _______________________________________________ >>>>>> OpenStack-dev mailing list >>>>>> OpenStack-dev@lists.openstack.org >>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> OpenStack-dev mailing list >>>>> OpenStack-dev@lists.openstack.org >>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>>> >>>> >>>> _______________________________________________ >>>> OpenStack-dev mailing list >>>> OpenStack-dev@lists.openstack.org >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>> >>> >>> What are the thoughts on when a 2.3.7 release is going to happen? I'm >>> specifically interested in getting the keystone v3 support [1] into a >>> released version of the library. >>> >>> 9/4 and feature freeze seems like a decent target date. >>> >> I can make that happen. I'll take a pass through the existing client >> reviews to see what's there, and roll another release which would >> include the keystone v3 work which is already merged. >> >> Thanks, >> Kyle >> >>> [1] https://review.openstack.org/#/c/92390/ >>> >>> -- >>> >>> Thanks, >>> >>> Matt Riedemann >>> >>> >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > I think we're at or near dependency freeze so wondering what the plan is for > cutting the final release of python-neutronclient before Juno release > candidates start building (which I think is too late for a dep update). > > Are there any Neutron FFEs that touch the client that people need to wait > for? > There are none at this point. I'll cut a client release either tomorrow (Sunday, 9-7) or Monday morning early Central time.
Thanks, Kyle > > -- > > Thanks, > > Matt Riedemann > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
