Hi Drew, I think it is really close to what you guessed. Here is how it goes as I have heard and seen,
1. Anybody (it can be a commiter or a non-commiter) can report a JIRA. 2. Commiters can assign a jira to himself and resolve them. (Non-commiters should apply patches, they can't directly assign or resolve jiras) 3. Normally the one who reported the jira should verify the fix and close it or reopen if it is not fixed. Even a non-commiter can close a JIRA reported by himself. 4. If the one who reported the jira is not closing it for a long time, a commiter can close it. Normally this is done near a release. On Thu, Apr 23, 2009 at 6:00 AM, Drew Baird (Volt) <[email protected]>wrote: > Hi all, > > What is the Apache Best Practice for resolving and closing Jira issues? > > I would think the developer would mark it resolved when he is finished and > then 'someone else" would close the issue after it has been verified. > > Comments from the the mentors would be appreaciated. > > Thanks! > Drew > > -- Thanks, Dimuthu Gamage http://www.dimuthu.org http://www.wso2.org
