bugzilla issue status change..

[Martin van den Bemt <mv...@mvdb.com>]

Hi,

I'm always a bit cautious if not hesitant to change messages in bugzilla,
since I'm not one of the developers. Some issues however I can easily give
an answer to. Should I indeed change the status of those kind of messages,
or just add my comments and leave it open, for someone with the bigger
picture / more knowledge about the issue?


Mvgr,
Martin


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: bugzilla issue status change..

[Bill Barker <wb...@wilshire.com>]

>
> I agree.  And don't be overly concerned with making a mistake and closing
> a report prematurely, since a developer could always reopen it.

And the person reporting it will almost certainly reopen it :).
>
> Thanks for your offer to help!
>
> >
> > Costin
> >
>
> Craig
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: bugzilla issue status change..

["Craig R. McClanahan" <cr...@apache.org>]

On Fri, 14 Dec 2001 costinm@covalent.net wrote:

> Date: Fri, 14 Dec 2001 07:19:22 -0800 (PST)
> From: costinm@covalent.net
> Reply-To: Tomcat Developers List <to...@jakarta.apache.org>
> To: Tomcat Developers List <to...@jakarta.apache.org>
> Subject: Re: bugzilla issue status change..
>
> On Fri, 14 Dec 2001, Martin van den Bemt wrote:
>
> > Hi,
> >
> > I'm always a bit cautious if not hesitant to change messages in bugzilla,
> > since I'm not one of the developers. Some issues however I can easily give
> > an answer to. Should I indeed change the status of those kind of messages,
> > or just add my comments and leave it open, for someone with the bigger
> > picture / more knowledge about the issue?
>
> Add comments, close it if it's trivial, close it if you're sure about the
> answer ( i.e. a bug that was already fixed, duplicates, etc ).
>

+1

> Leave it open if it's a bug or requires changes in the
> code/documentation/etc.
>
> That's IMHO - I think this would be a great contribution from anyone.
> 'Refining' the bug reports with test cases or extra details would also
> help a lot, and increase the chances of a bug to be fixed sooner.
>

I agree.  And don't be overly concerned with making a mistake and closing
a report prematurely, since a developer could always reopen it.

Thanks for your offer to help!

>
> Costin
>

Craig


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: bugzilla issue status change..

[co...@covalent.net]

On Fri, 14 Dec 2001, Martin van den Bemt wrote:

> Hi,
>
> I'm always a bit cautious if not hesitant to change messages in bugzilla,
> since I'm not one of the developers. Some issues however I can easily give
> an answer to. Should I indeed change the status of those kind of messages,
> or just add my comments and leave it open, for someone with the bigger
> picture / more knowledge about the issue?

Add comments, close it if it's trivial, close it if you're sure about the
answer ( i.e. a bug that was already fixed, duplicates, etc ).

Leave it open if it's a bug or requires changes in the
code/documentation/etc.

That's IMHO - I think this would be a great contribution from anyone.
'Refining' the bug reports with test cases or extra details would also
help a lot, and increase the chances of a bug to be fixed sooner.


Costin


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>