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.
|6 days ago|
|doc/source||1 month ago|
|specs||1 month ago|
|.coveragerc||3 years ago|
|.gitignore||4 years ago|
|.gitreview||6 days ago|
|.mailmap||4 years ago|
|.testr.conf||4 years ago|
|CONTRIBUTING.rst||4 years ago|
|LICENSE||4 years ago|
|MANIFEST.in||4 years ago|
|README.rst||4 months ago|
|requirements.txt||7 months ago|
|setup.cfg||2 years ago|
|setup.py||2 years ago|
|template.rst||4 years ago|
|test-requirements.txt||2 years ago|
|tox.ini||4 years ago|
This is a git repository for doing design review on enhancements to the OpenStack Project Infrastructure. This provides an ability to ensure that everyone has signed off on the approach to solving a problem early on.
Task: #<taskid>for the corresponding story's initial task is included as a footer in the commit message (see
CONTRIBUTING.rstfor relevant documentation links). This change should also add an entry for the proposed spec document in the
Approved Design Specificationssection of the
Once a specification is approved...
We don't always get everything right the first time. If we realize we need to revisit a specification because something changed, either we now know more, or a new idea came in which we should embrace, we'll manage this by proposing an update to the specification in question.