On Thu, Aug 09, 2007 at 03:32:43PM +1000, Don Brown wrote: > I believe the traditional purpose of the "closed" state is for a QA > department, so they can mark the issues they have verified to be > fixed. In Struts, I don't think we really do that, and while we do > informal code reviews (commit emails), we certainly don't require > formal test documents that verify the ticket resolution is correct. > If a release manager wants to take that role upon themselves, that's > great, but it should be purely optional.
I've rejigged JIRA to allow Closed issues to be edited, since that's been confusing/annoying a few people: https://issues.apache.org/jira/browse/INFRA-1303 (at least they will be on the next JIRA restart) Let me know if the Struts devs prefer to keep Closed issues uneditable. --Jeff > Don ... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
