On Thu, 22 Mar 2018 15:40:20 +0000, John Garbutt wrote:
On 20 March 2018 at 23:44, melanie witt <melwi...@gmail.com
<mailto:melwi...@gmail.com>> 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 think spec reviews, blueprint reviews, and code review topics could
all get a runway slot.
What if we had these queues:
Backlog Queue, Blueprint Runway, Approved Queue, Code Runway
Currently all approved blueprints would sit in the Approved queue.
As described, you leave the runway and go back in the queue if progress
stalls.
That might be a bit more complex than what I was thinking for our first
go at trying this process. Is "Backlog Queue" the list of unapproved
blueprints (specs) waiting for dedicated runway review and "Blueprint
Runway" are the specs guaranteed to receive review during the two week
time-box?
I hadn't been thinking about putting spec reviews into runways as well.
I had been focusing on only the review of implementations of approved specs.
Basically abandon the spec freeze. Control with runways instead.
I'm open to this idea, just had a concern as described in my last reply
to this thread, on whether getting rid of spec freeze may remove early
expectation setting for people (if they prefer that). I'm okay with
going with the majority vote about it.
-melanie
__________________________________________________________________________
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
