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 more structure and process in
order to focus review and complete merging of approved work more quickly
and reliably.

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.

The process and instructions are explained in detail on this etherpad,
which will also serve as the place we queue and track blueprints for
runways:

https://etherpad.openstack.org/p/nova-runways-rocky

Please bear with us as this is highly experimental and we will be giving
it a go knowing it's imperfect and adjusting the process iteratively as
we learn from it.

Okay, based on the responses on the discussion in the last nova meeting and this ML thread, I think we have consensus to go ahead and start using runways next week after the spec review day, so:

  Spec review day: Tuesday March 27

  Start using runways: Wednesday March 28

Please add your blueprints to the Queue if the requirements explained on the etherpad are met. And please ask questions, in #openstack-nova or on this thread, if you have any questions about the process.

We will be moving spec freeze out to r-2 (June 7) to lessen pressure on spec review while runways are underway, to get more time to review the current queue of approved implementations via runways, and to give ourselves the chance to approve more specs along the way if we find we're reducing the queue enough by completing blueprints.

Thanks,
-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

Reply via email to