Blacklist sphinx 2.1.0 (autodoc bug)
See https://github.com/sphinx-doc/sphinx/issues/6440 for upstream details Change-Id: I7675b45849a436d7968d212d7f6a2b373e9993fb
|2 months ago|
|doc/source||5 months ago|
|specs||5 months ago|
|.gitignore||2 years ago|
|.gitreview||7 months ago|
|.zuul.yaml||1 year ago|
|LICENSE||5 years ago|
|README.rst||6 months ago|
|requirements.txt||2 months ago|
|setup.cfg||10 months ago|
|setup.py||5 years ago|
|tox.ini||1 year ago|
This git repository is used to hold approved design specifications for changes to the Barbican 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:
You can find an example spec in 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 story in storyboard. Not all approved blueprints will get fully implemented.
Specifications have to be re-submitted 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:
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