Hmm. It's hard to think of a clear, definitive policy for these offhand. Perhaps we should take them case by case?
this particular one looks like it's begging to be closed. it's against an old, non-final release, and has been abandoned by the lone reporter. i'd vote to resolve that as "can't reproduce" and close it. On 9/18/05, Will Glass-Husain <[EMAIL PROTECTED]> wrote: > Hi, > > Continuing my quest of cleaning up the bug logs and driving towards a > specific release road map... > > What should we do with old JIRA issues that may or may not be fixed? For > example, this item... > > http://issues.apache.org/jira/browse/VELOCITY-129 > > Reported two years ago by a single user. No test case, no response to an > inquiry, no other users with that problem. I'm thinking of closing old, > single-occurrence, no test case issues like this one. (It can always be > re-opened). A shorter issue list might help us focus on the bugs that need > to be fixed. > > Or is that too harsh? > > Best, > WILL > > _______________________________________ > Forio Business Simulations > > Will Glass-Husain > phone (415) 440-7500 x89 > mobile (415) 235-4293 > [EMAIL PROTECTED] > www.forio.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
