Comment 11 for bug 297614

I do think the set of existing statuses bears on the introduction of new ones, because for example if someone considering adopting Launchpad browsed a project milestone page and saw a jumble of "Fix Committed" vs. "Fix Released" vs. "Fix Verified" vs. "Fix Failed", they might reasonably conclude it was too complicated, and flee. The same applies to potential QA volunteers for Ubuntu and other large projects. (Fixing bug 163694 would help in this case.)

Meanwhile on "Fix Failed": Who needs to know that a fix has been tried and didn't work, and for how long do they need to know it? A developer working on a second attempt at fixing a bug will presumably still need to use the "In Progress" and "Fix Committed" statuses to track that second fix, thereby causing the bug to lose its "Fix Failed" status. That suggests to me that whether a previous fix failed is orthogonal to the bug's current status, and therefore needs to be tracked somewhere other than status, even if that other place isn't a tag. Perhaps it could be auto-generated ... as Tom already suggested while I was writing this. :-)