[Tracker-discuss] [issue16] Automatic issue expiration

Brett C. metatracker at psf.upfronthosting.co.za
Thu Apr 2 07:46:55 CEST 2009


Brett C. <brett at python.org> added the comment:

On Wed, Apr 1, 2009 at 21:24, Senthil
<metatracker at psf.upfronthosting.co.za>wrote:

>
> Senthil <orsenthil at gmail.com> added the comment:
>
> I doubt if auto-closing if issue after a 14 day non-activity period is a
> good
> idea. The good way to analyze this change is, looking at the current issue
> tracker and seeing how many of the tickets have non-activity beyond 14
> days. If
> there is a huge number, that would give us an idea of churn it will create.
> This
> churn could be for good or bad. Looking the bad side, if the reporter did
> not
> get anyone in the nosy list,his bug will get lost and he may not care
> again.
>
> My sf.net bugs are open for months.
>
> My suggestion would be to send a remainder email with issue age in
> days,months
> or years to catch attention.

The closing of the issue should catch their attention. And commenting will
re-open it so it isn't hard to change the state. I still think that closing
a pending issue after 14 days is a good idea.

----------
nosy: +brett.cannon

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue16>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090402/8c7aaf55/attachment.htm>


More information about the Tracker-discuss mailing list