Blueprints should have a denied status
Bug #299533 reported by
Thomas Mashos
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
The status of blueprints is limited to things that basically say "yes we will do it, it's in progress, it's done" type things. There is no status definitions for not doing a blueprint for any particular reason. Launchpad should add items under "Definition Status" such as "Will not implement" or "Needs further information". Without these, some blueprints may sit in the blueprint queue with a new status forever.
"Obsolete" doesn't really work because that would be for a blueprint like "Improve ISA support"
Changed in launchpad: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in blueprint: | |
importance: | Medium → Low |
To post a comment you must log in.