diff --git a/doc/source/devref/sub_project_guidelines.rst b/doc/source/devref/sub_project_guidelines.rst index 975b9b19172..a0b45e7fac2 100644 --- a/doc/source/devref/sub_project_guidelines.rst +++ b/doc/source/devref/sub_project_guidelines.rst @@ -137,6 +137,9 @@ release. To release a sub-project, follow the following steps: +* First, follow the process found `here +`_ + for creating a bug for your release. * For projects which have not moved to post-versioning, we need to push an alpha tag to avoid pbr complaining. A member of the neutron-release group will handle this. diff --git a/doc/source/policies/bugs.rst b/doc/source/policies/bugs.rst index 679627c29c6..0c3b4fc3f20 100644 --- a/doc/source/policies/bugs.rst +++ b/doc/source/policies/bugs.rst @@ -71,15 +71,16 @@ It also worth adding that that some of these projects are part of the so called Neutron `stadium `_. Because of that, their release is managed centrally by the Neutron release team; requests for releases need to funnelled and screened -properly before they can happen. To this aim, the process should be like -the following: +properly before they can happen. To this aim, the process to request a release +is as follows: * Create a bug report to your Launchpad project: provide details as to what you would like to release; * Add Neutron to the list of affected projects. * Add 'release-subproject' tag to the list of tags for the bug report. * The Neutron release management team will watch these bugs, and work with - you to have the request fulfilled. + you to have the request fulfilled by following the instructions found `here +`_. .. _guidelines: