mirror of
https://opendev.org/openstack/barbican-specs.git
synced 2026-01-11 19:56:45 +00:00
Blueprints for the barbican project
Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1]. Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead [1] https://github.com/pypa/setuptools/commit/a2e9ae4cb Change-Id: I7ac3d0bd3eabbf1c23a5060b9f91b8a6c44336be |
||
|---|---|---|
| doc/source | ||
| specs | ||
| .gitignore | ||
| .gitreview | ||
| .zuul.yaml | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
==================================
OpenStack Barbican Specifications
==================================
.. image:: https://governance.openstack.org/badges/barbican-specs.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
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::
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
`story in storyboard`__. Not all approved blueprints will get fully implemented.
.. _Storyboard: https://storyboard.openstack.org/#!/project/openstack/barbican-specs
__ Storyboard_
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::
http://blueprints.launchpad.net/barbican
For more information about working with gerrit, see::
https://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.