On Jan 24, 2007, at 6:09 PM, Michael Koziarski wrote: > >> Anyhow, we can discuss this until we're blue in the face. At the end >> of the day what matters is how we behave. To that end *I* will >> continue to follow my own advice as to how to handle tickets for >> Rails, and I encourage others to do the same, if for no other reason >> than to contribute more test coverage to, and to inspire more >> confidence in the stability of, the best darn web framework out >> there. > > I think that in general, the onus is on the submitter to either > provide a failing test case, or simple steps to reproduce. If a > ticket gets closed prematurely, I figure there are a couple of > potential results: > > 0) it was invalid, everyone wins > 1) The submitter reopens it and provides more information on > reproducibility, everyone wins > 2) The submitter doesn't care any more and the bug stays closed. > everyone wins as we can go on to fix bugs which people care about. > 3) The submitter doesn't care any more, but someone submits a new bug. > the bug's either better documented, or the problem repeats. > > We don't have a dearth of users, and we're not penalising users who > submit invalid bugs. So I figure, err on the side of closing, reopen > with more information, not a bitchy comment. We're all after the same > thing here :)
+1. If you've observed a bug and you really want it fixed, but can't provide a patch (for whatever reason), a failing test case is the best way to "prove" that it is a bug. That's not to say that every bug report must include a failing test case, but if you don't provide it, you shouldn't be angry if no one else can verify what you've reported. I believe this is a common philosophy in most OSS projects. - Jamis --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
