>
> Ard Schrijvers hippo.nl> writes:
>
> > > It should be available in the list of possible actions
> (menu on the
> > > left), otherwise you do not have the appropriate rights.
> >
> > Yes that is my problem. These rights are related to being
> committer I suppose?
> > Is it something that
Ard Schrijvers hippo.nl> writes:
> > It should be available in the list of possible actions (menu on the
> > left), otherwise you do not have the appropriate rights.
>
> Yes that is my problem. These rights are related to being committer I suppose?
> Is it something that is arranged by infrastr
>
>
> Ard Schrijvers 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
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
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
Ard Schrijvers 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 c
>
> 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
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
s
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. IMH
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
ha
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
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
despi
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, i
* 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
14 matches
Mail list logo
