Blueprints for the barbican project
Go to file
zhouxinyong 44a26fd50f Delete the duplicate words in template.rst
Change-Id: Id2ea13e81a6c28321d99ec090f5f2c229dfa3302
2019-01-04 20:45:36 +08:00
doc/source Add Train specs directory 2018-11-14 14:41:10 +09:00
specs Delete the duplicate words in template.rst 2019-01-04 20:45:36 +08:00
.gitignore Ignore some files during running tox 2017-06-15 10:31:42 +07:00
.gitreview gitreview 2014-06-03 15:10:06 -05:00
.zuul.yaml import zuul job settings from project-config 2018-09-08 19:28:25 +02:00
LICENSE Add License and README 2014-05-15 14:02:39 -04:00
README.rst Update http to https. 2018-12-11 14:20:57 +08:00
requirements.txt Add RSS feed 2014-09-10 15:56:50 -04:00
setup.cfg Changed the home-page of barbican-specs in setup.cfg 2016-10-23 22:39:09 +05:30
setup.py First Pass at Doc Build 2014-05-19 20:56:54 -05:00
tox.ini Update min tox version to 2.0 2018-10-21 04:00:38 +00:00

README.rst

Team and repository tags

image

OpenStack Barbican Specifications

This git repository is used to hold approved design specifications for additions 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:

specs/<release>/

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.

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

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:

http://docs.openstack.org/infra/manual/developers.html#development-workflow

To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:

$ tox

After running tox, the documentation will be available for viewing in HTML format in the doc/build/ directory.