037adec4b8
Add a unit test that will check to make sure all top-level headings and sub-headings are present. The downside of this test is that it's going to fail on *every* merged spec if we add or change a heading to the template. Co-authored-by: Russell Bryant <rbryant@redhat.com> Change-Id: I1c15282e166fb3fe2e60fcf063a6cd822a3411ff
OpenStack Nova Specifications
This git repository is used to hold approved design specifications for additions to the Nova project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.
The layout of this repository is:
specs/<release>/You can find an example spec in doc/source/specs/template.rst.
Specifications are proposed for a given release by adding them to the specs/<release> directory and posting it for review. The implementation status of a blueprint for a given release can be found by looking at the blueprint in launchpad. Not all approved blueprints will get fully implemented.
Specifications have to be re-proposed for every release. The review may be quick, but even if something was previously approved, it should be re-reviewed to make sure it still makes sense as written.
Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:
http://blueprints.launchpad.net/novaPlease note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:
https://wiki.openstack.org/wiki/BlueprintsFor more information about working with gerrit, see:
https://wiki.openstack.org/wiki/Gerrit_Workflow