The new bug tracker is great! Just a couple of questions. Should
"resolve" send a message to the requester, or should we send a "reply"
as a policy to indicate the bug is fixed?
And should "comments" and "replys" be sent to the developers list, or
should the developers regularily check the website for comments on bugs
they have and/or are working on?
Thanks for the new system!
--
Sincerely,
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
People who think they know everything are very irritating to those
of us who do. ---Anonymous
Jazz and Trek Rule!!!
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Tue, Jan 09, 2001 at 11:51:21AM +0700, Justin Hickey wrote:
Hi all
The new bug tracker is great! Just a couple of questions. Should
"resolve" send a message to the requester, or should we send a "reply"
as a policy to indicate the bug is fixed?
And should "comments" and "replys" be sent to the developers list, or
should the developers regularily check the website for comments on bugs
they have and/or are working on?
Thanks for the new system!
Hi Justin, hi all,
even I am not sure how we document fixed bugs. Your v.digit bug
disappeared from the RT list (which is fine). But the "fixed" information
should be stored somewhere (at least in NEWS.html) to tell others
about it.
Bernhard, any ideas?
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Tue, Jan 09, 2001 at 11:51:21AM +0700, Justin Hickey wrote:
> Hi all
>
> The new bug tracker is great! Just a couple of questions. Should
> "resolve" send a message to the requester, or should we send a
> "reply" as a policy to indicate the bug is fixed?
>
> And should "comments" and "replys" be sent to the developers list,
> or should the developers regularily check the website for comments
> on bugs they have and/or are working on?
>
> Thanks for the new system!
Hi Justin, hi all,
even I am not sure how we document fixed bugs. Your v.digit bug
disappeared from the RT list (which is fine). But the "fixed"
information should be stored somewhere (at least in NEWS.html) to tell
others about it.
The reason it disappeared is that the status you are viewing is set to
"open". At the bottom of the page, select a status of either "any" or
"resolved" and the v.digit entry will appear again. But yes, I think we
need some indication of fixed bugs.
--
Sincerely,
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
People who think they know everything are very irritating to those
of us who do. ---Anonymous
Jazz and Trek Rule!!!
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Jan 11, 2001 at 09:51:54AM +0700, Justin Hickey wrote:
Hi Markus
Markus Neteler wrote:
>
> On Tue, Jan 09, 2001 at 11:51:21AM +0700, Justin Hickey wrote:
> > Hi all
> >
> > The new bug tracker is great! Just a couple of questions. Should
> > "resolve" send a message to the requester, or should we send a
> > "reply" as a policy to indicate the bug is fixed?
> >
> > And should "comments" and "replys" be sent to the developers list,
> > or should the developers regularily check the website for comments
> > on bugs they have and/or are working on?
> >
> > Thanks for the new system!
>
> Hi Justin, hi all,
>
> even I am not sure how we document fixed bugs. Your v.digit bug
> disappeared from the RT list (which is fine). But the "fixed"
> information should be stored somewhere (at least in NEWS.html) to tell
> others about it.
The reason it disappeared is that the status you are viewing is set to
"open". At the bottom of the page, select a status of either "any" or
"resolved" and the v.digit entry will appear again. But yes, I think we
need some indication of fixed bugs.
Ah - thanks for the hint!
I have added such a link at:
o The current development version is available at: CVS server
o The bug-tracking system is at: bug report form
o and here is the list of fixed bugs
From time to time I will feed this news file from the "resolved" list.
Like that we can track everything.
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'