OpenStack Workflow (Mistral) Specifications
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenDev Sysadmins aa6036c1e4 OpenDev Migration Patch 1 month ago
doc/source Fix doc generation for python 3 2 years ago
specs Add Train specs directory 7 months ago
tests Don't force policy specs into approved or implemented directories 2 years ago
.gitignore Switch to use stestr for unit test 11 months ago
.gitreview OpenDev Migration Patch 1 month ago
.stestr.conf Switch to use stestr for unit test 11 months ago
.zuul.yaml import zuul job settings from project-config 10 months ago
CONTRIBUTING.rst add CONTRIBUTING.rst 2 years ago
LICENSE Initial commit 3 years ago
README.rst Update links in README 10 months ago
requirements.txt Switch to use stestr for unit test 11 months ago
setup.cfg Change openstack-dev to openstack-discuss 6 months ago Initial commit 3 years ago
test-requirements.txt Update hacking version to latest 5 months ago
tox.ini Update min tox version to 2.0 7 months ago


Team and repository tags


OpenStack Workflow Engine Specifications

This git repository is used to hold approved design specifications for Mistral project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.

This would apply to new blueprints proposed in Mistral project from Mitaka, this new process provides a way to fast-track the feature history of Mistral, which is very useful for new comers to learn how Mistral evolves, where we are, and where we're going.

First, create a blueprint in launchpad and populate it with your spec's heading. Then, propose a spec following the template which can be found at specs/template.rst. This will be given an initial, high-level review to determine whether it is in scope and in alignment with project direction, which will be reflected on the review comments. If the spec is approved, you can continue with your code implementation, and update launchpad to set the specification URL to the spec's location on:

The Mistral PTL(or someone else on behalf of him) will update the release target, priority, and status accordingly.

If a specification has been approved but not completed within one or more releases since the approval, it may be re-reviewed to make sure it still makes sense as written. Specifications are proposed by adding them to the specs/<cycle>/approved directory and posting it for review. When a spec is fully implemented, it should be moved to specs/<cycle>/implemented.

You are welcome to submit patches associated with a blueprint, whose specification may have not been approved, but they will have a -2 ("do not merge") until the specification has been approved. This is to ensure that the patches don't get accidentally merged beforehand. You will still be able to get reviewer feedback and push new patch sets, even with a -2.