RE: Closing JIRA issues
On 10/11/06, Antonio Gallardo [EMAIL PROTECTED] wrote: ...IMHO, we should leave open this bug, because the fixi is not finished yet until we update excalibur... Same here. If update excalibur is a Jira or bugzilla issue somewhere, I'd make a link or a dependency to it to indicate what's happening. I am still a bit confused: I now have http://issues.apache.org/jira/browse/COCOON-1909, and added comment that it has been fixed, and needs a excalibur-xmlutil update. In excalibur-components, I created http://issues.apache.org/jira/browse/EXLBR-31 and added the patch file. Can I create some sort of dependency between the to, or do I need to make a cocoon JIRA issue that says update excalibur jars, and somehow relate http://issues.apache.org/jira/browse/COCOON-1909 to it (in principal, then when the update jira issue is closed, the 1909 should also be closed) Sry for the perhaps trivial questions, but I am just not (yet) familiar enough about the methodolies Ard -Bertrand
Re: Closing JIRA issues
Ard Schrijvers a.schrijvers at hippo.nl writes: Can I create some sort of dependency between the to, or do I need to make a cocoon JIRA issue that says update excalibur jars, and somehow relate http://issues.apache.org/jira/browse/COCOON-1909 to it (in principal, then when the update jira issue is closed, the 1909 should also be closed) COCOON-1909 should be directly linked to EXLBR-31 (I already did it). It should be available in the list of possible actions (menu on the left), otherwise you do not have the appropriate rights. Jörg
Re: Closing JIRA issues
Bertrand Delacretaz wrote: On 10/12/06, David Crossley [EMAIL PROTECTED] wrote: ...Closing issues prematurely is disrespectful... Agreed, with prematurely as the key aspect. I must admit I haven't looked at the particular issue being discussed, I was thinking in general terms: if an issue has been sitting here for several years, we've asked for feedback or additional info and nothing comes, I think it's fair to set it to won't fix. Only if feedback means stacktrace or any other essential information original submitter failed to furnish, then yes, such issue can be closed. But if feedback means please send in a patch... That's a different story. Not everybody can do a decent patch. Vadim
Re: Closing JIRA issues
On 10/12/06, Vadim Gritsenko [EMAIL PROTECTED] wrote: ...Only if feedback means stacktrace or any other essential information original submitter failed to furnish, then yes, such issue can be closed... But if feedback means please send in a patch... That's a different story. Not everybody can do a decent patch... 100% agreed! -Bertrand
Re: Closing JIRA issues
* Antonio Gallardo: Jean-Baptiste Quenot closed COCOON-1774. Resolution: Won't Fix Please reopen the issue if the problem persists with the new Dojo stuff. Thanks! I don't think it is the best way to close bugs. IMHO, the first part of a problem resolution is the problem identification and an open issue without a patch provides this first part. I would left open this bug (and onther of the current closed) until somebody comes with a solution. I don't know if you talked about this in GT2006, but if jira now becomes only a patch repository, I will like to know. At least we should vote for this policy change. Please don't take it personally. ;-) Hello Antonio, Sorry for the late reply, I missed your comment. Here is an explanation, I'm closing issues when: * it has been sitting in JIRA for a very long time * it is in « Feedback Required » state and reporter did not reply for a long time * no patch was provided * none of the Cocoon developers contributed to fix this issue or one of the developers says issue is already fixed I think there is no good reason to keep the issue open forever if no one intends to work on it, especially as the JIRA is full of these. BTW I discussed this with Vadim at the Hackathon. -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/
Re: Closing JIRA issues
Hi Ard, IMHO, we should leave open this bug, because the fixi is not finished yet until we update excalibur. Best Regards, Antonio Gallardo. Ard Schrijvers escribió: A different question, but related to closing issues practices: What is common practice for bugs that are reported in cocoon's jira, but are actually for example an excalibur bug? For example, I just fixed the bug regarding imported stylesheets not invalidating the parent-parent stylesheet despite when check-includes is set to true (http://issues.apache.org/jira/browse/COCOON-1909). But, it was in excalibur-xmlutil. So, the cocoon issue will be solved when a new excalibur release has been done, and the jars used by cocoon have been updated. What do I do with COCOON-1909 in the meantime? Is there some wiki page around with rules or guidelines according these kind of bugs (probably, but I just don't know where to look)? Thx for any explanation on the subject, Regards Ard On 10/11/06, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote: ...I think there is no good reason to keep the issue open forever if no one intends to work on it, especially as the JIRA is full of these... Agreed - if an issue sits in the feedback required for a long time and nothing happens, it means people are not interested in it anymore. Won't fix issues do not disappear anyway, they can be reopened if something concrete happens to them. -Bertrand
Re: Closing JIRA issues
On 10/11/06, Antonio Gallardo [EMAIL PROTECTED] wrote: ...IMHO, we should leave open this bug, because the fixi is not finished yet until we update excalibur... Same here. If update excalibur is a Jira or bugzilla issue somewhere, I'd make a link or a dependency to it to indicate what's happening. -Bertrand
Re: Closing JIRA issues
Jean-Baptiste Quenot wrote: * Antonio Gallardo: Jean-Baptiste Quenot closed COCOON-1774. Resolution: Won't Fix Please reopen the issue if the problem persists with the new Dojo stuff. Thanks! I don't think it is the best way to close bugs. IMHO, the first part of a problem resolution is the problem identification and an open issue without a patch provides this first part. I would left open this bug (and onther of the current closed) until somebody comes with a solution. I don't know if you talked about this in GT2006, but if jira now becomes only a patch repository, I will like to know. At least we should vote for this policy change. Please don't take it personally. ;-) Hello Antonio, Sorry for the late reply, I missed your comment. Here is an explanation, I'm closing issues when: I disagree with most of this. Why are you wanting to close such issues? Why don't we use Jira to classify them, and then use Jira filters to see what needs to be attended to? At Forrest for example, we try to regularly go through the open issues and schedule them to be attended to (Fix Version) for either the current release or the next release. Anything else is left in an unscheduled state. Then a Jira Filter shows us the roadmap. BTW I discussed this with Vadim at the Hackathon. * it has been sitting in JIRA for a very long time So what? That just shows that people are too busy or don't bother to look at Jira. * it is in Feedback Required state and reporter did not reply for a long time Okay, should be closed. * no patch was provided It is still an issue that needs attention. * none of the Cocoon developers contributed to fix this issue So what? That just shows that people are too busy or don't bother to look at Jira. or one of the developers says issue is already fixed Okay, should be closed. I think there is no good reason to keep the issue open forever if no one intends to work on it, especially as the JIRA is full of these. Closing issues prematurely is disrespectful. -David
