openstack/python-neutronclient
Code Issues Proposed changes

Update links in README

Browse Source 
Change the outdated links to the latest links in README

Change-Id: I70fbe513066b9375344e80308c646e56bf927db0
This commit is contained in:
XiaojueGuan 2018-06-12 16:17:56 +08:00
parent d090ea2751
commit 5a6b75655d
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.rst
View File

@ -2,8 +2,8 @@
Team and repository tags Team and repository tags
======================== ========================
.. image:: http://governance.openstack.org/badges/python-neutronclient.svg .. image:: https://governance.openstack.org/tc/badges/python-neutronclient.svg
:target: http://governance.openstack.org/reference/tags/index.html :target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on .. Change things from this point on

2
doc/source/contributor/transition_to_osc.rst
View File

@ -151,7 +151,7 @@ dual maintenance.
**Where does my CLI belong?** **Where does my CLI belong?**
If you are developing an API in any of the `neutron repos <http://governance.openstack.org/reference/projects/neutron.html>`_ If you are developing an API in any of the `neutron repos <https://governance.openstack.org/tc/reference/projects/neutron.html>`_
the client-side support must be generally located in either the openstackclient or neutronclient the client-side support must be generally located in either the openstackclient or neutronclient
repos. Whether the actual code goes into one or the other repo it depends on the nature of the repos. Whether the actual code goes into one or the other repo it depends on the nature of the
feature, its maturity level, and/or the depth of feedback required during the development. feature, its maturity level, and/or the depth of feedback required during the development.