openstack/neutron
Code Issues Proposed changes

Merge "Correct hyperlinks to sub_projects documentation"

Browse Source
This commit is contained in:
Jenkins
2016-06-03 14:14:29 +00:00
committed by Gerrit Code Review
parent 88710bbc6b 55d32ec40b
commit 658e99d7cd
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/devref/alembic_migrations.rst
View File

@@ -113,7 +113,7 @@ Neutron makes use of alembic branches for two purposes.
1. Independent Sub-Project Tables 1. Independent Sub-Project Tables
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Various `sub-projects <sub_projects.html>`_ can be installed with Neutron. Each Various `sub-projects <../stadium/sub_projects.html>`_ can be installed with Neutron. Each
sub-project registers its own alembic branch which is responsible for migrating sub-project registers its own alembic branch which is responsible for migrating
the schemas of the tables owned by the sub-project. the schemas of the tables owned by the sub-project.

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

@@ -90,7 +90,7 @@ and examples below. We'll describe best practices for:
Once you have everything in place you may want to add your project to the list 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 of Neutron sub-projects. Submit a patch via a gerrit review to neutron to add
your project to ``doc/source/devref/sub_projects.rst``. your project to ``doc/source/stadium/sub_projects.rst``.
Design and Development Design and Development
@@ -296,7 +296,7 @@ be the bare minimum you have to complete in order to get you off the ground.
here to initialize the remainder of the repository with other files being here to initialize the remainder of the repository with other files being
generated by the cookiecutter (like tox.ini, setup.cfg, setup.py, etc.). generated by the cookiecutter (like tox.ini, setup.cfg, setup.py, etc.).
* Create a repository on git.openstack.org (see `Official Sub-Projects * Create a repository on git.openstack.org (see `Official Sub-Projects
<http://docs.openstack.org/developer/neutron/devref/sub_projects.html>`_). For <http://docs.openstack.org/developer/neutron/stadium/sub_projects.html>`_). For
this you need the help of the OpenStack infra team. It is worth noting that 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 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, is the time you get to choose whether you want to start from a clean slate,