I know that the issue of closing tickets was brought up a couple of days ago and I'm hoping that others might be amniable to a suggestion regarding how tickets should be closed.
To me the best way to prepare a ticket for closing is to actually either a.) write a unit test which demonstrates that the ticket is not applicable or b.) point to a unit test which does the same. To just close a report with "works for me" or with "won't fix" seems to be dangerous at best, especially when it is a bug report. By going through the process of creating a unit test before closing we get the benefit of proof, plus the framework gets better test coverage and the test can provide the basis for additional tests in the future if more information is provided for the issue. Any thoughts on this? Does this seem like a reasonable thing to do? V/r Anthony Eden -- Cell: 808 782-5046 Current Location: Melbourne, FL --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
