Re: [openstack-dev] [nova] Review runways this cycle

On Tue, 20 Mar 2018 16:44:57 -0700, Melanie Witt wrote: As mentioned in the earlier "Rocky PTG summary - miscellaneous topics from Friday" email, this cycle we're going to experiment with a "runways" system for focusing review on approved blueprints in time-boxes. The goal here is to use a bit mo

Re: [openstack-dev] [nova] Review runways this cycle

On Thu, 22 Mar 2018 16:12:47 -0500, Matt Riedemann wrote: On 3/22/2018 2:59 PM, melanie witt wrote: And (MHO) I'm not sure we need help in reviewing more specs. I wholly disagree here. If you're on the core team, or want to be on the core team, you should be reviewing specs, because those are

Re: [openstack-dev] [nova] Review runways this cycle

On 3/22/2018 2:59 PM, melanie witt wrote: And (MHO) I'm not sure we need help in reviewing more specs. I wholly disagree here. If you're on the core team, or want to be on the core team, you should be reviewing specs, because those are the things that lay out the high level design and thinkin

Re: [openstack-dev] [nova] Review runways this cycle

WFM. November Oscar Victor Alpha you are cleared for takeoff. On 03/22/2018 03:18 PM, Matt Riedemann wrote: > On 3/22/2018 2:59 PM, melanie witt wrote: >> Maybe a good compromise would be to start runways now and move spec >> freeze out to r-2 (Jun 7). That way we have less pressure on spec >> re

Re: [openstack-dev] [nova] Review runways this cycle

On 3/22/2018 2:59 PM, melanie witt wrote: Maybe a good compromise would be to start runways now and move spec freeze out to r-2 (Jun 7). That way we have less pressure on spec review earlier on, more time to review the current queue of approved implementations via runways, and a chance to appro

Re: [openstack-dev] [nova] Review runways this cycle

On Thu, 22 Mar 2018 13:26:48 -0500, Eric Fried wrote: I think the only concern around moving spec freeze out would be that I thought the original purpose of the spec freeze was to set expectations early about what was approved and not approved instead of having folks potentially in the situatio

Re: [openstack-dev] [nova] Review runways this cycle

> I think the only concern around moving spec freeze out would be that I > thought the original purpose of the spec freeze was to set expectations > early about what was approved and not approved instead of having folks > potentially in the situation where it's technically "maybe" for a large > ch

Re: [openstack-dev] [nova] Review runways this cycle

On Thu, 22 Mar 2018 15:40:20 +, John Garbutt wrote: On 20 March 2018 at 23:44, melanie witt > wrote: We were thinking of starting the runways process after the spec review freeze (which is April 19) so that reviewers won't be split between spec reviews

Re: [openstack-dev] [nova] Review runways this cycle

On Thu, 22 Mar 2018 10:38:38 -0500, Matt Riedemann wrote: On 3/20/2018 6:44 PM, melanie witt wrote: We were thinking of starting the runways process after the spec review freeze (which is April 19) so that reviewers won't be split between spec reviews and reviews of work in runways. I'm going

Re: [openstack-dev] [nova] Review runways this cycle

Hi So I am really excited for us to try runways out, ASAP. On 20 March 2018 at 23:44, melanie witt wrote: > We were thinking of starting the runways process after the spec review > freeze (which is April 19) so that reviewers won't be split between spec > reviews and reviews of work in runways.

Re: [openstack-dev] [nova] Review runways this cycle

On 3/20/2018 6:44 PM, melanie witt wrote: We were thinking of starting the runways process after the spec review freeze (which is April 19) so that reviewers won't be split between spec reviews and reviews of work in runways. I'm going to try and reign in the other thread [1] and bring it back

[openstack-dev] [nova] Review runways this cycle

Hello Stackers, As mentioned in the earlier "Rocky PTG summary - miscellaneous topics from Friday" email, this cycle we're going to experiment with a "runways" system for focusing review on approved blueprints in time-boxes. The goal here is to use a bit more structure and process in order to