Browse Source

Update links in README

 Change the outdated links to the latest links in README

Change-Id: I38ca6433f132d57d3fce5c14abfb5dd104af7e38
XiaojueGuan 10 months ago
parent
commit
952de11031
1 changed files with 4 additions and 4 deletions
  1. 4
    4
      specs/newton/neutron-stadium.rst

+ 4
- 4
specs/newton/neutron-stadium.rst View File

@@ -60,7 +60,7 @@ Proposed Change
60 60
 
61 61
 The Neutron Stadium is the list of projects that show up in the following document:
62 62
 
63
-http://governance.openstack.org/reference/projects/neutron.html
63
+https://governance.openstack.org/tc/reference/projects/neutron.html
64 64
 
65 65
 The list includes projects that the Neutron PTL and core team are directly
66 66
 involved in, and manage on a day to day basis. To do so, the PTL and team
@@ -95,8 +95,8 @@ projects and should not be perceived as particularly stringent:
95 95
    and robustness of a project;
96 96
  * good release footprint, according to the chosen release model;
97 97
  * adherence to deprecation and stable backports policies;
98
- * demonstrated ability to do `upgrades <http://governance.openstack.org/reference/tags/assert_supports-upgrade.html>`_
99
-   and/or `rolling upgrades <http://governance.openstack.org/reference/tags/assert_supports-rolling-upgrade.html>`_,
98
+ * demonstrated ability to do `upgrades <https://governance.openstack.org/tc/reference/tags/assert_supports-upgrade.html>`_
99
+   and/or `rolling upgrades <https://governance.openstack.org/tc/reference/tags/assert_supports-rolling-upgrade.html>`_,
100 100
    where applicable;
101 101
  * adoption of neutron-lib (with related hacking rules applied), and proof
102 102
    of good decoupling from Neutron core internals; having unit tests executed
@@ -163,7 +163,7 @@ openstack.org namespace, as outlined in the `creator guide <http://docs.openstac
163 163
 Furthermore, projects that interact with Neutron purely via its REST API should
164 164
 also be incentivized to seek other forms of governance, such as applying as
165 165
 top-level OpenStack project and follow the new project requirements as outlined
166
-by the `OpenStack Governance <http://governance.openstack.org/reference/new-projects-requirements.html>`_,
166
+by the `OpenStack Governance <https://governance.openstack.org/tc/reference/new-projects-requirements.html>`_,
167 167
 rather than going for Stadium inclusion.
168 168
 Drivers that leverage proprietary software and/or hardware will also not be
169 169
 considered for inclusion into the Neutron Stadium, due to the barrier on

Loading…
Cancel
Save