On 2011-06-19 00:30, Benson Margulies wrote: > I just looked at the 'blocker' issues. We have a variety of very old > JIRAs here. None of the ones I looked at have a self-contained test > case that would can be downloaded, run, and converted to an > integration test, etc.
This is one of the major obstacles we have at the Maven project. The sheer amount of old and sometimes really old issues in JIRA. For the last couple of years I've pinged reporters of new issues straight away for test cases, if none was attached to a new issue. But as you say there are lots of old ones that are practically impossible to resolve without some kind of test case. Maybe we should plan a JIRA cleanup day? Let's find a date where some of us on the dev team can work together to clean up old issues. We announce that together with your proposed letter to the users list as well. > What's the policy? My temptation would be to comment on them asking if > the OP is still interested (in some cases, 5 years later), and, if so, > can they come up with a repeatable test case, and if not close as not > a real bug. I've done this kind of thing for plugins in the past. For those I have opted to close the issue as "Incomplete", because it lacks a reproducible test case. > I don't mind in some cases doing work to build a test case, but to go > to all this trouble for a bug that was opened about maven 2.0.x, where > it may not be that easy to reconstruct the critical components of the > problem, seems a dubious use of time. Agreed. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
