Comment 425 for bug 195698

There are many bugs which have been open three years and haven't been fixed. We don't fix bugs solely on the basis of how long they've been opened. We consider the severity of the bad behavior, likelihood the typical user will hit it, the frequency at which the bad behavior is hit, interaction with other potential bugfixes or existing bugs, and at certain periods during release cycles (as now) the complexity of the fix and the estimated time to stabilize the functionality and address regressions. (I may have forgotten one or two criteria, but these hit most of the high points.) Taking everything in total, it's been deferred so far, but as there's been recent (taking into account crunch time for the 3.5 release) work on patches here, I think you have good reason to hope this bug may be fixed in the near future. That said, there are no promises: if you want promises regarding a bug, pay someone to fix it for you (and if you want that fix in future releases and not just your own custom build, pay someone to fix it *right*).

In any case, your complaints add nothing substantial to this bug and make it more difficult to approach this bug (did you really read all 257 comments before yours?). Indeed, after 259 comments it's difficult to say *anything* other than patches or review comments are substantial. Finally, consider also that every useless comment spams 140-odd people.

In summary: complaints about a bug and requests for status updates have no place in bug comments because they make bugs harder to read while simultaneously spamming large numbers of people.