Russell Bryant 11b2254f43 Fix a sphinx docs error
Comment out specs/juno/* until a spec merges so that the docs can
build without errors.

There is still one warning about man pages with this change in place,
but I believe it will require a change to pbr to suppress.

Change-Id: Id63da83ce6e60c444322072e68c17c97cf983846
2014-03-31 11:55:40 -04:00
2014-03-31 11:55:40 -04:00
2014-03-14 23:09:48 +00:00
2014-03-24 16:28:41 -04:00
2014-03-24 16:28:41 -04:00
2014-03-31 11:39:55 -04:00

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/nova

Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:

https://wiki.openstack.org/wiki/Blueprints

For more information about working with gerrit, see:

https://wiki.openstack.org/wiki/Gerrit_Workflow
Description
OpenStack Compute (Nova) Specifications
Readme 60 MiB
Languages
Python 90.3%
Shell 9.7%