openstack/nova
Code Issues Proposed changes

Clarify the approval process of specless blueprints

Browse Source 
Add a paragraph which clarifies that a specless blueprint needs to
be approved and the normal process for doing so, with links to
additional information.

Change-Id: I1d4fc40a2e5acb8b63f90e00dc19ee5a65fbe870
This commit is contained in:
Chris Dent
2016-11-15 17:14:57 +00:00
parent fb693f07f0
commit 56658310ba
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/blueprints.rst
View File

@@ -37,6 +37,11 @@ Guidelines for when a feature doesn't need a spec.
* API changes always require a design discussion.
When a blueprint does not require a spec it still needs to be
approved before the code which implements the blueprint is merged.
Specless blueprints are discussed and potentially approved during
the `Open Discussion` portion of the weekly `nova IRC meeting`_. See
`trivial specifications`_ for more details.
Project Priorities
===================
@@ -63,3 +68,6 @@ Project Priorities
* The blueprint approval team, to help find the right balance of blueprints
* Contributors looking for something to work on
* People looking for what they can expect in the next release
.. _nova IRC meeting: http://eavesdrop.openstack.org/#Nova_Team_Meeting
.. _trivial specifications: https://specs.openstack.org/openstack/nova-specs/readme.html#trivial-specifications