Group Based Policy Design Specifications
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
OpenDev Sysadmins b9e720faf4 OpenDev Migration Patch vor 7 Monaten
doc/source Fixing the deprecated library function. vor 3 Jahren
specs Dual-stack L3-Policy mapping vor 2 Jahren
tests tox doesn't fail anymore at the py27 environment vor 4 Jahren
.gitignore Adding some missing repo artifacts vor 5 Jahren
.gitreview OpenDev Migration Patch vor 7 Monaten
.testr.conf Adding some missing repo artifacts vor 5 Jahren
LICENSE Initial commit with GBP spec and repo artifacts vor 5 Jahren
README.rst Workflow documentation is now in infra-manual vor 5 Jahren
requirements.txt Adding some missing repo artifacts vor 5 Jahren
setup.cfg Initial commit with GBP spec and repo artifacts vor 5 Jahren
setup.py Initial commit with GBP spec and repo artifacts vor 5 Jahren
tox.ini Initial commit with GBP spec and repo artifacts vor 5 Jahren

README.rst

Group Based Policy Specifications

This git repository is used to hold approved design specifications for additions to the Group Based Policy 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. A skeleton that contains all the sections required for a spec file is located in doc/source/specs/skeleton.rst and can be copied, then filled in with the details of a new blueprint for convenience.

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.

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. Please do not check in the generated HTML files as a part of your commit.