Completed blueprints should filter out "Obsolete" blueprints

Bug #1712685 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Stackalytics
New
Undecided
Unassigned

Bug Description

This is similar to bug 1447287 but not exactly the same.

Looking at http://stackalytics.com/?module=nova-group&metric=bpc&release=pike it shows 51 completed blueprints, but launchpad shows 50:

https://blueprints.launchpad.net/nova/pike

This is the difference:

http://stackalytics.com/report/blueprint/nova/hyper-v-spawn-on-neutron-event

https://blueprints.launchpad.net/nova/+spec/hyper-v-spawn-on-neutron-event

Note it's marked obsolete and implemented because it was fixed via a bug.

It looks like https://review.openstack.org/179146 is why it's considered a completed blueprint for Pike, because it was marked obsolete and completed within the Pike series timeframe, but it's not actually a valid blueprint, it was just fixed via a bug and marked obsolete.

So it seems stackalytics should ignore 'obsolete' blueprints even if they are marked as implemented. If a blueprint is obsolete because it was implemented by some other blueprint, then it should be superseded in launchpad, not marked obsolete.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.