> Is it the policy of the Rails project that defect reports without a > verifiable test case are invalid and will be closed? >
I guess that'll be a nice policy to have considering number of open tickets trac has. Well, that seems to be an undocumented policy, a good thing anyways. > I'm not sure it's a practical proposition > -- most people don't "get" testing, and plenty of Rails' users aren't > sufficiently good programmers to be able to write a solid test case for > something as complex as Rails. > Let them use core mailing list then. Which is a perfect medium. > So mark them "more info required" with a note that they need to have more > info attached or they'll be closed in N days/weeks/months. > That'd be same as closing as "incomplete". > <advocate type="devil"> > That cuts both ways, though -- I, as a developer, don't have time to debug a > problem in Rails. That problem isn't mine -- I didn't write the buggy code > that's causing the hassle. It's *your* fault, dammit. > </advocate> Oh well. That wasn't really needed. May be you can elaborate on *your* part. > Going back to my original point, though, about actively *closing* tickets > that document *real* bugs that are trivially verifiable[1] simply because > the patch isn't sufficient is only reasonable in one circumstance -- if > defect reports without test cases are summarily closed. I haven't seen that > policy documented anywhere (and I would imagine something that it would want > to be in big letters on the front page), and in fact the exact opposite is > stated on the dev front page -- "Tickets are fine". I'm just reporting an > irritating inconsistency in the handling of tickets, biased against > well-meaning but insufficiently clued contributors (which are the sort of > people I'd be wanting to encourage, not discourage, if it were my project). > Perfect in theory. But practically speaking, if there is a problem that affects majority of people, it won't go unnoticed. And otherwise, people can always use this very mailing list. The reason why I'm in favor of actively closing tickets without patches/verifying tests is the current state of trac. 100s of open tickets. And a tiny % of them are valid bugs. And because of that, many of the proper patches go unnoticed for long time. They just get "lost". --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
