This note is about when XalanJ2 committers might resolve and close JIRA issues that are getting old and stale. Read on if you are interested in the details.
- Brian - - - - - - - - - - - - - - - - - - - - Brian Minchau Apache Xalan PMC Member e-mail: [EMAIL PROTECTED] ================================================================== At todays meeting for active XalanJ2 committers the issue came up on when to move a JIRA issue to "Resolved" status, and when to move an issue in "Resolved" status to "Closed" status. There is a Status field for JIRA issues with these choices: - Open - In Progress - Resolved - Reopened - Closed For JIRA issues moved to "Resolved" status there is an associated JIRA Resolution field with these choices: - Fixed - Won't Fix - Duplicate - Incomplete - Cannot Reproduce (see http://www.atlassian.com/software/jira/docs/latest/issues.html#StatusTypes for more detailed descriptions). There are a number of JIRA issues at http://issues.apache.org/jira/secure/Dashboard.jspa that are open against the XalanJ2 project, but with insufficient information to investigate or fix the issue. For example a testcase may have been requested, but never given. The XalanJ2 committers agreed that if there is no response to requests for more information, that we may resolve the issue after a month of non-response. In this situation the resolution would most likely be "Incomplete" or "Cannot Reproduce". A resolved issue should be closed by the reporter when the reporter agrees that the resolution is correct. Our decision was that a JIRA issue may be closed by a XalanJ2 committer if it was resolved before a new release was published, and after a new release became available a request to the reporter to close the issue down, that is to verify the resolultion, had no response from the reporter. I'm not a lawyer, I think you get the drift of what I am trying to say. There are a number of old JIRA issues and the Xalan Java team would like to clean some of the old dormant issues off the books. I would guess that a number of the reporters don't respond because they have moved on to other things. I'm sorry if some of them are dormant because of a lack of activity from the Xalan Java team, but we are volunteers, and other things can keep us from working full-time on these issues. We welcome new Xalan contributors, who will turn into committers, who will help us fix these bugs! Get in contact through [email protected] - Brian Minchau
