OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|2 months ago|
|doc/source||2 years ago|
|specs||7 months ago|
|tests||2 years ago|
|.gitignore||11 months ago|
|.gitreview||2 months ago|
|.stestr.conf||11 months ago|
|.zuul.yaml||10 months ago|
|CONTRIBUTING.rst||2 years ago|
|LICENSE||3 years ago|
|README.rst||10 months ago|
|requirements.txt||11 months ago|
|setup.cfg||6 months ago|
|setup.py||3 years ago|
|test-requirements.txt||5 months ago|
|tox.ini||7 months ago|
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
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.