|Zuul 4801e2f143||1 day ago|
|doc||2 weeks ago|
|specs||1 day ago|
|.gitignore||6 years ago|
|.gitreview||1 year ago|
|.testr.conf||6 years ago|
|.zuul.yaml||2 years ago|
|LICENSE||6 years ago|
|README.rst||2 years ago|
|setup.cfg||5 months ago|
|setup.py||6 years ago|
|test-requirements.txt||2 years ago|
|tox.ini||5 months ago|
This git repository is used to hold approved design specifications for additions to the Tacker 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 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.
Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:
Launchpad blueprints for Tacker can be found at:
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
doc/build/ directory. Please do not checkin the generated HTML files as a part of your commit.