Cross link sub-project release processes
Cross link the release processes for sub-projects across the devref and bug policy documentation. Change-Id: Ifa548fc61777e13a0131b681610babf212b42e27 Signed-off-by: Kyle Mestery <mestery@mestery.com>
This commit is contained in:
parent
c522cee596
commit
874fd5b61a
@ -137,6 +137,9 @@ release.
|
||||
|
||||
To release a sub-project, follow the following steps:
|
||||
|
||||
* First, follow the process found `here
|
||||
<http://docs.openstack.org/developer/neutron/policies/bugs.html#plugin-and-driver-repositories>`_
|
||||
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.
|
||||
|
@ -71,15 +71,16 @@ It also worth adding that that some of these projects are part of the so
|
||||
called Neutron `stadium <http://governance.openstack.org/reference/projects/neutron.html#deliverables-and-tags>`_.
|
||||
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
|
||||
<http://docs.openstack.org/developer/neutron/devref/sub_project_guidelines.html#sub-project-release-process>`_.
|
||||
|
||||
|
||||
.. _guidelines:
|
||||
|
Loading…
Reference in New Issue
Block a user