Specs for packetary project
Go to file
Ivan Bogomazov bd8d86825a Add 0.2.0 spec
Change-Id: I3104a473c2ee914e2c7be3fb114d72a1af901d90
2016-06-06 15:40:13 +03:00
doc/source Add 0.2.0 spec 2016-06-06 15:40:13 +03:00
specs Add 0.2.0 spec 2016-06-06 15:40:13 +03:00
tests Initial commit 2016-03-18 16:50:12 +03:00
tools Initial commit 2016-03-18 16:50:12 +03:00
.gitignore Initial commit 2016-03-18 16:50:12 +03:00
.gitreview Added .gitreview 2016-02-29 13:14:41 +00:00
.testr.conf Initial commit 2016-03-18 16:50:12 +03:00
AUTHORS Add 0.2.0 spec 2016-06-06 15:40:13 +03:00
ChangeLog Add 0.2.0 spec 2016-06-06 15:40:13 +03:00
LICENSE Initial commit 2016-03-18 16:50:12 +03:00
README.rst Initial commit 2016-03-18 16:50:12 +03:00
requirements.txt Initial commit 2016-03-18 16:50:12 +03:00
setup.cfg Initial commit 2016-03-18 16:50:12 +03:00
setup.py Initial commit 2016-03-18 16:50:12 +03:00
tox.ini Initial commit 2016-03-18 16:50:12 +03:00

Packetary Specifications

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

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.