diff --git a/doc/source/devref/alembic_migrations.rst b/doc/source/devref/alembic_migrations.rst index 3c5b28fd11b..307d05ead8b 100644 --- a/doc/source/devref/alembic_migrations.rst +++ b/doc/source/devref/alembic_migrations.rst @@ -113,7 +113,7 @@ Neutron makes use of alembic branches for two purposes. 1. Independent Sub-Project Tables ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Various `sub-projects `_ 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 the schemas of the tables owned by the sub-project. diff --git a/doc/source/devref/contribute.rst b/doc/source/devref/contribute.rst index 28552953e1a..aa51d94221b 100644 --- a/doc/source/devref/contribute.rst +++ b/doc/source/devref/contribute.rst @@ -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 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 @@ -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 generated by the cookiecutter (like tox.ini, setup.cfg, setup.py, etc.). * Create a repository on git.openstack.org (see `Official Sub-Projects - `_). For + `_). 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,