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
