31335bcf21
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using these versions will allow especially: * Linking from HTML to PDF document * Allow parallel building of documents * Fix some rendering problems Update Sphinx version as well. Set openstackdocs_pdf_link to link to PDF file. Note that the link to the published document only works on docs.openstack.org where the PDF file is placed in the top-level html directory. The site-preview places the PDF in a pdf directory. Disable openstackdocs_auto_name to use 'project' variable as name. Change pygments_style to 'native' since old theme version always used 'native' and the theme now respects the setting and using 'sphinx' can lead to some strange rendering. openstackdocstheme renames some variables, so follow the renames before the next release removes them. A couple of variables are also not needed anymore, remove them. See also http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html Change-Id: I7b38486e0dadef1dc6184c8bbc9d63a9a2e832cd |
||
|---|---|---|
| doc | ||
| specs | ||
| tests | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
README.rst
Team and repository tags
OpenStack Sahara Specifications
This git repository is used to hold approved design specifications for additions to the Sahara 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 for Sahara specifications is:
specs/<release>/The layout of this repository for Sahara Client is:
specs/saharaclient/When a new version of Sahara Client is released the implemented blueprints will be moved to a directory specific to that release:
specs/saharaclient/<release>/The layout of this repository for Sahara Tests is:
specs/sahara-tests/You can find an example spec in specs/template.rst.
For specifications that have been reviewed and approved but have not been implemented:
specs/backlog/Specifications in this directory indicate the original author has either become unavailable, or has indicated that they are not going to implement the specification. The specifications found here are available as projects for people looking to get involved with Sahara. If you are interested in claiming a spec, start by posting a review for the specification that moves it from this directory to the next active release. Please set yourself as the new primary assignee and maintain the original author in the other contributors list.
Specifications are proposed for a given release by adding them to the
specs/<release> directory and posting it for review.
Not all approved blueprints will get fully implemented. The
implementation status of a blueprint for a given release can be found by
looking at the tasks associated to the corresponding story in
Storyboard.
Incomplete 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 and for the Juno-1 development milestone, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:
https://blueprints.launchpad.net/saharaLaunchpad blueprints are no more used for tracking the current status of blueprints. For historical information, see:
https://wiki.openstack.org/wiki/BlueprintsFor more information about working with gerrit, see:
https://docs.openstack.org/infra/manual/developers.html#development-workflowTo validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:
$ toxAfter running tox, the documentation will be available
for viewing in HTML format in the doc/build/ directory.