[Kdenlive-devel] To close or not to close... that is the question (about old feedback issues)

[Cinephiliac]

On Sunday 23 November 2008 01:22:08 Dan Dennedy wrote:
> On Sat, Nov 22, 2008 at 9:21 PM, Cinephiliac <bugsbane at gmail.com> wrote:
> > We have issues awaiting user feedback as old as February. I'm wondering
> > how many reminders we send people, and how long we let feedback items sit
> > before closing them down, or do we leave them open indefinitely?
>
> The SourceForge tracker's "Pending" status waits 2 weeks before
> automatically closing it. I have used this, but I make certain to not
> abuse it. Basically, if I can not reproduce it, and I think it is
> specific to their environment/system, then I use it after requesting
> feedback. However, if it is a segfault with some backtrace, for
> example, then I would not use it even if it went unresponsive. I leave
> these open in the hope someone else who sees the same problem will
> comment. However, after a long while and several versions, I will
> close these too as then I consider them no longer relevant.

So here's the average use case:

User files a bug report / feature request that is unclear, making it difficult to 
understand what the issue is. There's usually no backtrace.  It's marked as 
feedback, but time goes by and we don't hear from them again.

I feel that some kind of reminder is needed, as a single email is easily 
missed. One reminder seems enough. The question is after how long, and then 
how long before it just gets closed (assuming no backtrace or reproducible 
issue)?

Two weeks (to a reminder), one week (to close) is probably better than 1 month 
/ 1 week now I think about it as they're more likely still interested, 
available and at the same email address.

What does everyone else think?