On Mon, 8 Oct 2012, Remy Blank wrote:
Many of these are actually right, but most aren't worth the effort to fix
them immediately or at all. But closing them would also be wrong. So
depending on the fact how you handle tickets it must not be bad, that you
accumulate them. As long as you at least care for these which are
important (these, where there are requests of state, additional info -
these where there is activity).
Keeping tickets open that we are very unlikely to ever fix sends the
wrong message, and leads to comments like "What, this extremely
important bug is still not fixed after five years? WTF!" as we see them
here from time to time (fortunately not too often). We could close them
as "value-to-work-ratio-too-low-sorry" to make that clear, but then we
would have people re-open them with a comment like "This can't be right,
this extremely important bug must absolutely be fixed!", so I'm not sure
we would gain anything.
Well, a "still not fixed after five years" is actually a note, that
probably the bug has higher importance than thought before...
Also together with the voting system it allows to express user opinion
about bugs.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
