openstack/governance
Code Issues Proposed changes

Amend the spelling error of a word

Browse Source 
Change-Id: I67f80727126ffda8b91af50020189172d1d1d2cd
This commit is contained in:
chengebj5238 2018-06-06 16:29:18 +08:00
parent 94abc873f1
commit 1df34813d4
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
goals/queens/split-tempest-plugins.rst
View File

@ -222,7 +222,7 @@ The barbican project does not have in-tree tempest plugin.
Completion Artifacts: Completion Artifacts:
The barbican team is maintaining it's tempest plugin in a seperate repo: The barbican team is maintaining it's tempest plugin in a separate repo:
http://git.openstack.org/cgit/openstack/barbican-tempest-plugin http://git.openstack.org/cgit/openstack/barbican-tempest-plugin
@ -273,7 +273,7 @@ The cloudkitty project does not have in-tree tempest plugin.
Completion Artifacts: Completion Artifacts:
The cloudkitty team is maintaining it's tempest plugin in a seperate repo: The cloudkitty team is maintaining it's tempest plugin in a separate repo:
http://git.openstack.org/cgit/openstack/cloudkitty-tempest-plugin http://git.openstack.org/cgit/openstack/cloudkitty-tempest-plugin
@ -495,7 +495,7 @@ The kuryr project does not have in-tree tempest plugin.
Completion Artifacts: Completion Artifacts:
The kuryr team is maintaining it's tempest plugin in a seperate repo: The kuryr team is maintaining it's tempest plugin in a separate repo:
http://git.openstack.org/cgit/openstack/kuryr-tempest-plugin http://git.openstack.org/cgit/openstack/kuryr-tempest-plugin
@ -584,7 +584,7 @@ The murano project does not have in-tree tempest plugin.
Completion Artifacts: Completion Artifacts:
The murano team is maintaining it's tempest plugin in a seperate repo: The murano team is maintaining it's tempest plugin in a separate repo:
http://git.openstack.org/cgit/openstack/murano-tempest-plugin http://git.openstack.org/cgit/openstack/murano-tempest-plugin
@ -845,7 +845,7 @@ The solum project does not have in-tree tempest plugin.
Completion Artifacts: Completion Artifacts:
The solum team is maintaining it's tempest plugin in a seperate repo: The solum team is maintaining it's tempest plugin in a separate repo:
http://git.openstack.org/cgit/openstack/solum-tempest-plugin http://git.openstack.org/cgit/openstack/solum-tempest-plugin
@ -936,7 +936,7 @@ The tripleo project does not have in-tree tempest plugin.
Completion Artifacts: Completion Artifacts:
The tripleo team is maintaining its tempest plugin in a seperate repo for The tripleo team is maintaining its tempest plugin in a separate repo for
testing tripleo workflows: testing tripleo workflows:
http://git.openstack.org/cgit/openstack/tripleo-common-tempest-plugin http://git.openstack.org/cgit/openstack/tripleo-common-tempest-plugin
@ -995,7 +995,7 @@ The os-win project does not have in-tree tempest plugin.
Completion Artifacts: Completion Artifacts:
The Winstackers team is maintaining its tempest plugin in a seperate repo: The Winstackers team is maintaining its tempest plugin in a separate repo:
http://git.openstack.org/cgit/openstack/oswin-tempest-plugin http://git.openstack.org/cgit/openstack/oswin-tempest-plugin
@ -1019,6 +1019,6 @@ Planning Artifacts:
Completion Artifacts: Completion Artifacts:
The Zun team is maintaining its tempest plugin in a seperate repo: The Zun team is maintaining its tempest plugin in a separate repo:
https://git.openstack.org/cgit/openstack/zun-tempest-plugin https://git.openstack.org/cgit/openstack/zun-tempest-plugin

2
resolutions/20180307-trademark-program-test-location.rst
View File

@ -62,7 +62,7 @@ and the Trademark Program.
.. note:: No overarching direction is provided here on what tooling must be .. note:: No overarching direction is provided here on what tooling must be
used in the tests but it is generally expected that the tooling used in the tests but it is generally expected that the tooling
should be aggreed by the people who are reviewing the code. If a should be agreed by the people who are reviewing the code. If a
project wants to use tooling other than the core tempest libraries project wants to use tooling other than the core tempest libraries
(e.g., gabbi_) they should prefer a project specific plugin and be (e.g., gabbi_) they should prefer a project specific plugin and be
aware that their choice of tooling may limit the ability for aware that their choice of tooling may limit the ability for