Why is there no "fix proposed" status?

Asked by Martin Ling

I recently came across a bug in a project which I am not a developer for.

I tracked down the problem to a simple mistake in the code, produced and tested a patch, and attached it to the bug report.

This still leaves the bug at the "Confirmed" stage. It is one of a large number of bugs in this state, most of which the developers seem to have yet to look at.

It would be nice to be able to bring attention to the fact that a fix is already available; it just needs a developer to commit it to the repository. For a developer looking through the bugs in their package, bugs in this state should be quicker to tackle than "Confirmed" or "Triaged" bugs, where the cause is unknown or the fix has yet to be written.

But there is no bug status available between "In progress" (which discourages developers from looking at the report, because someone else is tackling it) and "Fix committed" (which is not yet true). It seems that a "Fix proposed" or perhaps "Fix contributed" status would be a useful intermediate status for the not uncommon scenario where a fix is contributed by a user.

I would consider filing this as a Launchpad wishlist bug, but I wanted to ask first whether this is an issue that has been discussed already and rejected for some reason.

Question information

English Edit question
Launchpad itself Edit question
Deryck Hodge Edit question
Solved by:
Deryck Hodge
Last query:
Last reply:
2009-10-07 mrevell: Deryck, could you please answer this?
Revision history for this message
Best Deryck Hodge (deryck) said :

Hi, Martin.

There has been some bugs filed around better tracking or reporting of patches. Take a look at the tag "patch-tracking" (https://bugs.edge.launchpad.net/malone/+bugs?field.tag=patch-tracking) which has some bugs related to your question. Particularly, you might be interested in bug 180388.


Revision history for this message
Martin Ling (martin-launchpad) said :

Thanks Deryck Hodge, that solved my question.