Hi folks!

As you can see below, we have to make the final release of python-ironic-inspector-client really soon. We have 2 big missing parts:

1. Introspection rules support.
   I'm working on it: https://review.openstack.org/#/c/223096/
This required a substantial requirement, so that our client does not become a complete mess: https://review.openstack.org/#/c/223490/

2. Support for getting introspection data. John (trown) volunteered to do this work.

I'd like to ask the inspector team to pay close attention to these patches, as the deadline for them is Friday (preferably European time).

Next, please have a look at the milestone page for ironic-inspector itself: https://launchpad.net/ironic-inspector/+milestone/2.2.0 There are things that require review, and there are things without an assignee. If you'd like to volunteer for something there, please assign it to yourself. Our deadline is next Thursday, but it would be really good to finish it earlier next week to dedicate some time to testing.

Thanks all, I'm looking forward to this release :)


-------- Forwarded Message --------
Subject: Re: [openstack-dev] [all][ptl][release] final liberty cycle client library releases needed
Date: Tue, 15 Sep 2015 10:45:45 -0400
From: Doug Hellmann <d...@doughellmann.com>
Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org>
To: openstack-dev <openstack-dev@lists.openstack.org>

Excerpts from Dmitry Tantsur's message of 2015-09-15 16:16:00 +0200:
On 09/14/2015 04:18 PM, Doug Hellmann wrote:
> Excerpts from Doug Hellmann's message of 2015-09-14 08:46:02 -0400:
>> PTLs and release liaisons,
>>
>> In order to keep the rest of our schedule for the end-of-cycle release
>> tasks, we need to have final releases for all client libraries in the
>> next day or two.
>>
>> If you have not already submitted your final release request for this
>> cycle, please do that as soon as possible.
>>
>> If you *have* already submitted your final release request for this
>> cycle, please reply to this email and let me know that you have so I can
>> create your stable/liberty branch.
>>
>> Thanks!
>> Doug
>
> I forgot to mention that we also need the constraints file in
> global-requirements updated for all of the releases, so we're actually
> testing with them in the gate. Please take a minute to check the version
> specified in openstack/requirements/upper-constraints.txt for your
> libraries and submit a patch to update it to the latest release if
> necessary. I'll do a review later in the week, too, but it's easier to
> identify the causes of test failures if we have one patch at a time.

Hi Doug!

When is the last and final deadline for doing all this for
not-so-important and non-release:managed projects like ironic-inspector?
We still lack some Liberty features covered in
python-ironic-inspector-client. Do we have time until end of week to
finish them?

We would like for the schedule to be the same for everyone. We need the
final versions for all libraries this week, so we can update
requirements constraints by early next week before the RC1.

https://wiki.openstack.org/wiki/Liberty_Release_Schedule

Doug


Sorry if you hear this question too often :)

Thanks!

>
> Doug
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to