On Sun, Oct 7, 2012 at 6:19 PM, Remy Blank <[email protected]> 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. > Does t.e.o have a keyword for these kinds of tickets? As a non-core-developer I'd like to help out and also get more familiar with the core codebase, and little bugs that aren't worth a core dev's time to fix sound like they might be good tickets to start on. Or maybe moving them into a special milestone would make it clear that no core dev is likely to look at these, and also make them easy for someone like me to find? Along the same lines, does t.e.o have any way for a non core developer to mark a ticket "has a patch, which works, [ideally has tests,] and "just" needs a core developer to review the patch? I might be misunderstanding the nature of these tickets though ... I'm hoping you're talking about little bugs that aren't worth the time to reproduce and fix, rather than little bugs that require design decisions and new configuration settings or swappable components. :-) -- 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.
