[openstack-dev] [tripleo] Blueprints moved out to Rocky
aschultz at redhat.com
Mon Dec 11 18:31:13 UTC 2017
On Fri, Dec 8, 2017 at 6:11 PM, Moshe Levi <moshele at mellanox.com> wrote:
> Hi Alex,
> I don't see the tripleo ovs hardware offload feature. The spec was merge into queens , but for some reason the blueprint is not in approve state .
Just as a reminder it's everyone's responsibility to make sure their
blueprints are properly up to date. I've mentioned this in the weekly
meeting a few times in the last month. I've added the patches
from this email into the blueprint for tracking
> I has only 3 patches left:
> 1. https://review.openstack.org/#/c/507401/ has 2 +2
> 2. https://review.openstack.org/#/c/507100/ has 1 +2
> 3. https://review.openstack.org/#/c/518715/
> I would appreciated if we can land all the patches to queens release.
We should be able to land these and they appear to be in decent shape.
Please reach out on irc if you aren't getting additional reviews on
these. It would be really beneficial to land these in the new week or
so if possible.
>  - https://review.openstack.org/#/c/502313/
>  - https://blueprints.launchpad.net/tripleo/+spec/tripleo-ovs-hw-offload
>> -----Original Message-----
>> From: Alex Schultz [mailto:aschultz at redhat.com]
>> Sent: Saturday, December 9, 2017 1:34 AM
>> To: OpenStack Development Mailing List (not for usage questions)
>> <openstack-dev at lists.openstack.org>
>> Subject: [openstack-dev] [tripleo] Blueprints moved out to Rocky
>> Hey folks,
>> So I went through the list of blueprints and moved some that were either not
>> updated or appeared to have a bunch of patches not in a mergable state.
>> Please take some time to review the list of blueprints currently associated
>> with Rocky to see if your efforts have been moved. If you believe you're
>> close to implementing the feature in the next week or two, let me know and
>> we can move it back into Queens. If you think it will take an extended period
>> of time (more than 2 weeks) to land but we need it in Queens, please submit
>> an FFE.
>> If you have an blueprint that is currently not in implemented in Queens,
>> please make sure to update the blueprint status if possible. For the ones I
>> left in due to the patches being in a decent state, please make sure those get
>> merged in the next few weeks or we will need to push them out to Rocky.
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-
>> request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev