On 25 February 2011 13:38, mmcnickle <[email protected]> wrote: > > On Feb 25, 3:17 am, Gabriel Hurley <[email protected]> wrote: > >> - May intimidate new contributors to see that their ticket was "closed". >> - Doesn't discount the fact that there may be a valid issue here which we >> don't want to forget about. > > I wouldn't underestimate either of these 2 points. The PHP core team > "close" issues that need replies/more info, or simply haven't gained > any attention after a month. Coming from a reporter of a few of those > issues, I can say it is extremely offputting as it's (in PHP's case) > almost impossible to get those tickets out of that state, even if more > info has been supplied. Many valid bugs were shelved/forgotten for > lack of interest.
I don't see this being an issue in Django. If you provide more info, then you can change the state to "reopened" and someone else will take a look at it, just as they would with any other ticket. > > Trac also doesn't seem to search "closed" tickets, so you may have an > increase in duplicate bugs being reported. Do you mean this search: http://code.djangoproject.com/search?q=something ? It finds closed tickets to me. -- Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en.
