openstack
/
neutron
Code Issues Proposed changes

Remove references to defunct Stadium docs 

Change-Id: I4f755e88bfbe19e58de81dc7ec4d12a26a43c8c0
Closes-Bug: #1656297
This commit is contained in:
John Davidge 2017-01-13 13:48:50 +00:00
parent 1a528e817f
commit f57dbf3f13
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/devref/contribute.rst
View File

@ -89,8 +89,9 @@ and examples below. We'll describe best practices for:
* Documentation;
Once you have everything in place you may want to add your project to the list
of Neutron sub-projects. Submit a patch via a gerrit review to neutron to add
your project to ``doc/source/stadium/sub_projects.rst``.
of Neutron sub-projects. See `Adding or removing projects to the stadium
<http://docs.openstack.org/developer/neutron/stadium/governance.html#adding-or-removing-projects-to-the-stadium>`_
for details.
Design and Development
@ -295,8 +296,7 @@ be the bare minimum you have to complete in order to get you off the ground.
want to skip this step now, build the history first (next step), and come back
here to initialize the remainder of the repository with other files being
generated by the cookiecutter (like tox.ini, setup.cfg, setup.py, etc.).
* Create a repository on git.openstack.org (see `Official Sub-Projects
<http://docs.openstack.org/developer/neutron/stadium/sub_projects.html>`_). For
* Create a repository on git.openstack.org. For
this you need the help of the OpenStack infra team. It is worth noting that
you only get one shot at creating the repository on git.openstack.org. This
is the time you get to choose whether you want to start from a clean slate,

2
doc/source/policies/bugs.rst
View File

@ -138,7 +138,7 @@ called Neutron `stadium <http://governance.openstack.org/reference/projects/neut
Because of that, their release is managed centrally by the Neutron
release team; requests for releases need to be funnelled and screened
properly before they can happen. Release request process is described `here
<http://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html#sub-project-release-process>`_.
<http://docs.openstack.org/developer/neutron/stadium/guidelines.html#releases>`_.
.. _guidelines: