On 7/5/2016 4:31 AM, Balázs Gibizer wrote:
-----Original Message-----
From: Matt Riedemann [mailto:[email protected]]
Sent: July 01, 2016 23:03
We're now past non-priority feature freeze. I've started going through
some blueprints and -2ing them if they still have outstanding changes. I
haven't gone through the full list yet (we started with 100).
I'm also building a list of potential FFE candidates based on:
I'm proposing 5 of the remaining notification transformations patches
as FFE candidates. [1]
1. How far along the change is (how ready is it?), e.g. does it require
a lot of change yet? Does it require a Tempest test and is that passing
already? How much of the series has already merged and what's left?
The below patches are all ready but they needed a rebase after the
last minute changes on the instance.delete patch which they depend on.
Tempest test is not required for these patches.
already had +2 +W:
* https://review.openstack.org/329089 Transform instance.suspend notifications
already had +2:
* https://review.openstack.org/331972 Transform instance.restore notifications
* https://review.openstack.org/332696 Transform instance.shelve notifications
ready for core review
* https://review.openstack.org/329141 Transform instance.pause notifications
* https://review.openstack.org/329255 Transform instance.resize notifications
The spec-ed scope of the bp [1] is already merged but these are fairly trivial
patches
2. How much core reviewer attention has it already gotten?
See above.
3. What kind of priority does it have, i.e. if we don't get it done in
Newton do we miss something in Ocata? Think things that start
deprecation/removal timers.
If we move these to Ocata then we slow the notifications transformation
work which means the deprecation of the legacy notifications
also moves further in the future.
Cheers,
Gibi
[1]
https://blueprints.launchpad.net/nova/+spec/versioned-notification-transformation-newton
The plan is for the nova core team to have an informal meeting in the
#openstack-nova IRC channel early next week, either Tuesday or
Wednesday, and go through the list of potential FFE candidates.
Blueprints that get exceptions will be checked against the above
criteria and who on the core team is actually going to push the changes
through.
I'm looking to get any exceptions completed within a week, so targeting
Wednesday 7/13. That leaves a few days for preparing for the meetup.
--
Thanks,
Matt Riedemann
__________________________________________________________
________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-
[email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
We agreed to FFE anything that's already got a +2, but anything else
that's not ready needs to wait for Ocata, including new notification
transformation patches.
--
Thanks,
Matt Riedemann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
