I'm pretty sure I can work this into my schedule. I'll just check the bug queue first thing each morning, if you want me to do this.


Eric Lavarde wrote:

Dimitry Polivaev wrote:
I'd be more blunt in my approach: if, after a reasonable amount of effort,
we can't reproduce it, we just close it. I did it recently for one of the
bugs, putting it pending to give the user a chance to react (OK, it was
also so that he/she provided next to no information).
The only remaining question are about who could spend his time in 
evaluating the requests and whether he is allowed to close the requests 
that seems to be wrong (or set them to pending status so that the 
originator can response).

I do it from time to time, and check bugs, assign them to the one or the 
other developers, etc... But a few more helpers from our community could 
be of help (I think I made a proposal in this direction a while ago).
If there is an agreement on the principle, and if an admin is ready to 
give the necessary rights to the nominated users, I could drive this (or 
someone else, Ray?).

FYI: I have done an experience that some of the bugs can be demonstrated 
only with some J2SE versions.
Well, that's why we need to make sure that the reporter tells us the 
exact Java version. On the other hand, my experience is also that such 
issues are actually Java bugs you can google for (but not always probably).




This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Freemind-developer mailing list