From 3e085ec97c4a8d77398e70c0db78ae0849dda841 Mon Sep 17 00:00:00 2001 From: Kyle Mestery Date: Wed, 6 May 2015 14:50:57 +0000 Subject: [PATCH] Update the specs process for Liberty This adds explicit wording around the fact we will not use a deadline for specs submission during Liberty. It also adds wording around the new requirement for a less heavy-weight template to be filled in when submitting a spec. Change-Id: Id54550fb4314117db8fcfea90dd0627899e80c74 --- doc/source/policies/blueprints.rst | 61 +++++++++++++++++++++++++----- 1 file changed, 51 insertions(+), 10 deletions(-) diff --git a/doc/source/policies/blueprints.rst b/doc/source/policies/blueprints.rst index 50ab9e766..91aaf1da5 100644 --- a/doc/source/policies/blueprints.rst +++ b/doc/source/policies/blueprints.rst @@ -1,19 +1,60 @@ Blueprints and Specs ==================== -The Neutron team uses the `neutron-specs `_ -repository for it's specification reviews. Detailed information can be found -`here `_. Please also find additional -information in the reviews.rst file. +The Neutron team uses the `neutron-specs +`_ repository for it's +specification reviews. Detailed information can be found `here +`_. Please also find +additional information in the reviews.rst file. + +The Neutron team does not enforce deadlines for specs and blueprints. These +can be submitted throughout the release cycle. The drivers team will review +this on a regular basis throughout the release, and based on the load for the +milestones, will assign these into milestones or move them to the backlog +for selection into a future release. + +Please note that we use a `template +`_ +for spec submissions. It is not required to fill out all sections in the +template. Review of the spec may require filling in information left out by +the submitter. Neutron BP and Spec Notes ------------------------- -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: +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 work flow to get the spec +into the next release is as follows: + +* The PTL will create a -backlog directory during the RC window and + move all specs which didn't make the 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. + +Neutron Feature Requests +------------------------ + +We are introducing the concept of feature requests. Feature requests are +tracked as Launchpad bugs, tagged with the new 'RFE' tag, and allow for +the submission and review of these feature requests before code is submitted. +This allows the team to verify the validity of a feature request before the +process of submitting a neutron-spec is undertaken, or code is written. It +also allows the community to express interest in a feature by subscribing to +the bug and posting a comment in Launchpad. Note the temptation to game the +system exists, but given the history in Neutron for this type of activity, it +will not be tolerated and will be called out as such in public on the mailing +list. -* The PTL will create a -backlog directory during the RC window and move all specs which didn't make the there. -* Anyone can propose a patch to neutron-specs which moves a spec from the previous release into the new release directory. +RFEs can be submitted by anyone and by having the community vote on them in +Launchpad, we can gauge interest in features. The drivers team will evaluate +these on a weekly basis along with the specs. -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. +The process for moving work from RFEs into the code involves someone assigning +themselves the RFE bug and filing a matching spec in the neutron-specs +repository. The spec will then be reviewed by the community and approved by +the drivers team before landing in a release. This is the same process as +before RFFs existed in Neutron. -- 2.45.2