Update sphinx requirements
Following recent changes to global requirements , we need to update sphinx requirements locally.  If558f184c959e4b63b56dec3ca1571d1034cfe5c Change-Id: I64c67c8da327a44e73e30e95ba9a7dae4fb5b6fb
|23 hours ago|
|doc/source||8 months ago|
|priorities||7 months ago|
|specs||2 days ago|
|tests||1 year ago|
|.gitignore||1 year ago|
|.gitreview||1 month ago|
|.stestr.conf||1 year ago|
|.zuul.yaml||9 months ago|
|LICENSE||5 years ago|
|README.rst||1 year ago|
|requirements.txt||23 hours ago|
|setup.cfg||5 months ago|
|setup.py||5 years ago|
|test-requirements.txt||2 months ago|
|tox.ini||7 months ago|
This git repository is used to hold approved design specifications for additions to the Baremetal Provisioning program, and in particular, the Ironic 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/approved/ specs/backlog/ specs/not-implemented/ specs/<release>/ specs/<juno|kilo|liberty>-implemented/
There are also placeholder directories for old links that have been moved.
Specifications must follow the template which can be found at specs/template.rst.
Specifications are proposed by adding them to the specs/approved directory, adding a soft link to it from the specs/not-implemented directory, and posting it for review. When a specification is fully implemented, the link in specs/not-implemented directory should be moved to the appropriate specs/<release> directory. Not all approved specifications will get fully implemented.
Starting with the Mitaka development cycle, all approved specifications (implemented and not-implemented) will reside in the specs/approved directory.
Also starting with the Mitaka development cycle, our Launchpad bug tracking system is used for tracking the work related to a specification. (This replaces the use of Launchpad blueprints). The bug should be tagged with 'rfe', its title should be prefixed with '[RFE]' and the Importance should be set to 'Wishlist'. For existing RFE bugs, see:
Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:
For more information about working with gerrit, see:
To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:
tox, the documentation will be available for viewing in HTML format in the
To quickly preview just the rst syntax rendering (without Sphinx features) of a single spec file execute the following command:
$ tox -evenv rst2html.py <path-to-your-spec.rst> <path-to-output.html>
<path-to-output.html> in your browser. Running full
tox is still advised before submitting your patch.