From: armando-migliaccio Date: Wed, 7 Oct 2015 04:11:26 +0000 (-0700) Subject: Improvements to the RFE management process X-Git-Url: https://review.fuel-infra.org/gitweb?a=commitdiff_plain;h=7d14ede04916d5129cab12e57ebbec93bd6c2b4d;p=openstack-build%2Fneutron-build.git Improvements to the RFE management process The Drivers team realized that with the current model, RFE bugs were never off their radar even though RFE proposals were approved and ready to be worked on. As a result it was becoming tricky to handle the RFE backlog during the drivers meeting. These changes are aimed at keeping the list of RFE bugs to a manageable size, irrespective of how fast code gets submitted and merged: the responsibilities of vetting feature proposals and reviewing code are very much different, and this policy changes try to reflect that. Change-Id: I37b7f1b7c3538e871cb9bc5cbfba61d99858f16f --- diff --git a/doc/source/policies/blueprints.rst b/doc/source/policies/blueprints.rst index 0c2d67ede..1b2899e91 100644 --- a/doc/source/policies/blueprints.rst +++ b/doc/source/policies/blueprints.rst @@ -38,9 +38,10 @@ release however. Neutron Request for Feature Enhancements ---------------------------------------- -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. +In Liberty the team introduced 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 @@ -66,18 +67,45 @@ The workflow for the life an RFE in Launchpad is as follows: * As soon as a member of the neutron-drivers team acknowledges the bug, it will be moved into the "Confirmed" state. No priority, assignee, or milestone is set at this time. -* The bug goes into the "Triaged" state once a discussion around the RFE has - taken place. +* The bug goes into the "Triaged" state while the discussion is ongoing. * The neutron-drivers team will evaluate the RFE and may advise the submitter to file a spec in neutron-specs to elaborate on the feature request. * The PTL will work with the Lieutenant for the area being identified by the RFE to evaluate resources against the current workload. * In either case (a spec being required or not), once discussion has happened the bug will get an assignee, priority and milestone. -* Once a patchset targeting the bug is submitted the bug will move into the - "In Progress" state. -* When all patches targeting the bug are merged or abandoned, the bug will be - moved to the "Completed" state. +* At this point, the RFE is 'approved', and its tag will move from 'rfe' to + 'rfe-approved'. From now on, the bug becomes just a regular bug report and + it will follow the usual 'In Progress', 'Fix Committed', 'Fix Released' + transition when code gets posted/merged/released, respectively. +* If the code fails to merge, the bug report may be marked as incomplete, + unassigned and untargeted, and it will be garbage collected by + the Launchpad Janitor if no-one takes over in time. Renewed interest in the + feature will have to go through RFE submission process once again. + +In summary: + ++------------+-----------------------------------------------------------------------------+ +|State | Meaning | ++============+=============================================================================+ +|New | This is where all RFE's start, as filed by the community. | ++------------+-----------------------------------------------------------------------------+ +|Confirmed | Drivers/LTs - Move to this state to mean, "yeah, I see that you filed it" | ++------------+-----------------------------------------------------------------------------+ +|Triaged | Drivers/LTs - Move to this state to mean, "discussion is ongoing" | ++------------+-----------------------------------------------------------------------------+ +|Won't Fix | Drivers/LTs - Move to this state to reject an RFE. | ++------------+-----------------------------------------------------------------------------+ + +Once the triaging (discussion is complete) and the RFE is approved, the tag goes from 'rfe' +to 'rfe-approved', and at this point the bug report goes through the usual state transition. + +The drivers team will be discussing the following bug reports during their IRC meeting: + +* `New RFE's `_ +* `Confirmed RFE's `_ +* `Triaged RFE's `_ + Cutover to RFEs From Pure Specs ------------------------------- diff --git a/doc/source/policies/bugs.rst b/doc/source/policies/bugs.rst index b2a5d6ce7..f21f7e526 100644 --- a/doc/source/policies/bugs.rst +++ b/doc/source/policies/bugs.rst @@ -314,7 +314,9 @@ more will be added over time if needed. +-------------------------------+---------------------------------------+----------------------+ | release-subproject_ | A request to release a subproject | Kyle Mestery | +-------------------------------+---------------------------------------+----------------------+ -| rfe_ | Feature enhancements | Drivers Team | +| rfe_ | Feature enhancements being screened | Drivers Team | ++-------------------------------+---------------------------------------+----------------------+ +| rfe-approved_ | Approved feature enhancements | Drivers Team | +-------------------------------+---------------------------------------+----------------------+ | sg-fw_ | A bug affecting security groups | Kevin Benton | +-------------------------------+---------------------------------------+----------------------+ @@ -552,6 +554,14 @@ RFE * `RFE - All bugs `_ * `RFE - In progress `_ +.. _rfe-approved: + +RFE-Approved +++++++++++++ + +* `RFE-Approved - All bugs `_ +* `RFE-Approved - In progress `_ + .. _sriov-pci-pt: SRIOV-PCI PASSTHROUGH