openstack/neutron
Code Issues Proposed changes

Merge "Add language around re-proposing specs for new releases"

Browse Source
This commit is contained in:
Jenkins 2015-03-29 17:02:23 +00:00 committed by Gerrit Code Review
commit 9f67818cc6
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/source/policies/blueprints.rst
View File

@ -6,5 +6,14 @@ repository for it's specification reviews. Detailed information can be found
`here <https://wiki.openstack.org/wiki/Blueprints#Neutron>`_. Please also find additional `here <https://wiki.openstack.org/wiki/Blueprints#Neutron>`_. Please also find additional
information in the reviews.rst file. information in the reviews.rst file.
Please note that at the start of each cycle, any BP/spec which did not make it in the release Neutron BP and Spec Notes
will need to be resubmitted and approved for the next cycle. -------------------------
There are occasions when a spec will be approved and the code will not land in the cycle it was targeted at. For these cases,
the workflow to get the spec into the next release is as follows:
* The PTL will create a <release>-backlog directory during the RC window and move all specs which didn't make the <release> there.
* Anyone can propose a patch to neutron-specs which moves a spec from the previous release into the new release directory.
The specs which are moved in this way can be fast-tracked into the next release. Please note that it is required to re-propose
the spec for the new release however.