Devref contains a document discussing project priorities. Include a
link to the list of specific Kilo priorities that lives over in the
nova-specs repo.
Change-Id: I1770447b03df1cc1ab029780fada96fab8ccaa0f
At the nova mid-cycle we agreed that while specs have made our blueprint
process significantly better, we think the current approach still leaves
much to be desired. This document is the outcome of the discussion at
the mid-cycle on how we want to manage blueprints in Kilo.
This proposal is being placed in devref, as we want to use gerrit's
workflow (two core reviews, inline comments, revisions etc) and this is
a document for developers.
Introduce the idea of project priorities.
Change-Id: I7075a130c01be22f3ee5315d4a65b8e524b5a1ad
At the nova mid-cycle we agreed that while specs have made our
process significantly better, we think the current approach still leaves
much to be desired. This document is the outcome of the discussion at
the mid-cycle on how we want to manage blueprints in kilo.
This proposal is being placed in devref, as we want to use gerrit's
workflow (two core reviews, inline comments, revisions etc) and this is
a document for developers.
It turns out adding the specs requirement to blueprints adds a
non-trivial amount of overhead, revisit when a blueprint and spec is
needed to minimize overhead in cases where it isn't helpful.
Change-Id: Iaaadc26f3f51ee091419beaa12e0508623eed99e