Like most OpenStack projects, Nova uses blueprints and specifications (specs) to track new features, but not all blueprints require a spec. This document covers when a spec is needed.
Note
Nova’s specs live at: specs.openstack.org
A spec is needed for any feature that requires a design discussion. All features need a blueprint but not all blueprints require a spec.
If a new feature is straightforward enough that it doesn’t need any design
discussion, then no spec is required. In order to provide the sort of
documentation that would otherwise be provided via a spec, the commit
message should include a DocImpact
flag and a thorough description
of the feature from a user/operator perspective.
Guidelines for when a feature doesn’t need a spec.
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.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.