summit should not key on bp definition state

[Steve Langasek]

When a blueprint in launchpad has a definition state other than 'new', 'discussion', or 'drafting', summit will not import it for scheduling. This is an unnecessary constraint that causes confusion every 6 months, because blueprints that have been carried over or resurrected from a previous cycle may have a different state and it's easy to forget to look at this.

Checking the definition state is an unnecessary constraint. If the blueprint has been targeted to the sprint, it should be available for scheduling; if someone decides it shouldn't be scheduled, it should be un-targeted from the sprint. And if summit really wants to care about getting the definition states right, we should try to implement this as some kind of automatic email notification to the track leads, so these don't fall off the radar. (But I'd rather we just get rid of the check.)

[Steve Langasek (vorlon)]

Per Chris Johnston, this filtering is happening not in summit, but in the launchpad API export of blueprints. So we need to fix this in Launchpad.

[Chris Johnston (cjohnston)]

Steve, FWIW, there will need to be a change in Summit after this is completed.. Either the other definitions will need to be added or or the whole status field be removed.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r16566 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/16566>.