Clarify how we milestones are assigned

Milestone assignment is another mumbo jumbo effort in open source.
Artificially setting milestones implies that someone can reliably
predict the future when no-one is really in full control.

For this reason let's make clear that we optmistically target the
current milestone for work that is supposed to start asap, and
complete sooner rather than later. Rolling over until the work is
complete is the natural course of action.

Dashboards [1] then capture the entire workload (BP and RFE) for
the entire release cycle, and that's helpful to provide to overall
view.

[1] https://launchpad.net/neutron/+milestone/<release>-?

Change-Id: Idb2d84ba683d2c8f1460e7bf0ff76d457cf42bce

diff --git a/doc/source/policies/blueprints.rst b/doc/source/policies/blueprints.rst
index 219557f6dd6848f484e3ade21293280e9cc2bfdf..80c55b0d89c2c54a9482a4dd79ffe52e910f251b 100644 (file)
--- a/doc/source/policies/blueprints.rst
+++ b/doc/source/policies/blueprints.rst
@@ -150,12 +150,15 @@ The workflow for the life an RFE in Launchpad is as follows:
   the work planned. Blueprints for which resources cannot be identified
   will have to be deferred.
 
-* In either case (a spec being required or not), once discussion has happened
-  the bug will get an assignee, priority and milestone.
-* 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.
+* In either case (a spec being required or not), once the discussion has
+  happened and there is positive consensus on the RFE, the report is 'approved',
+  and its tag will move from 'rfe' to 'rfe-approved'.
+* At this point, the RFE needs resources, and if none are identified for
+  some time the report will be marked incomplete.
+* As for setting the milestone (both for RFE bugs or blueprints), the current
+  milestone is always chosen, assuming that work will start as soon as the feature
+  is approved. Work that fails to complete by the defined milestone will roll
+  over automatically until it gets completed or abandoned.
 * 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