Just took a look at the bugtracker again.
Still we should utilise it more, thus I write this nice reminder.
There are about 15 unclassified entries,
which probably are bugs but some could be wishes.
About 37 bugs have not been touched for over half a year.
It does not seem likely that we do not have any update information.
So please have a look at if you have updated information enter them
or a pointer to them into the bugtracker.
This might be important for people who reported so they
can give more details.
We do not use priorities and assignments yet.
Markus: If you know if the bugs are in somebodies
working area, you could start to assign bugs to them?
Well the developer in question can of course does not
need to keep ownership of the bug or fix it themself,
just to give a bit of guidance.
We should just start using priorities for bugs and wishes.
I think a rule of thump is that wishes should be
lower as bugs.
We could also have a rule of thump up to when bugs should be
fixed for next immediate releases and give them priorities over 70.
If we cannot recreate a bug, we should put it on stalled.
If we release a new version these bug reporters should be contacted
and the bug closed if they cannot recreate the bug a second time
with the new version.
It is so good to see bugs squashed bugtracker.
It documents the nice work of the development team.
Bernhard
--
Professional Service around Free Software (intevation.net)
The FreeGIS Project (freegis.org)
Association for a Free Informational Infrastructure (ffii.org)
FSF Europe (fsfeurope.org)
On Thu, Nov 08, 2001 at 04:54:44PM +0100, Bernhard Reiter wrote:
So please have a look at if you have updated information enter them
or a pointer to them into the bugtracker.
This might be important for people who reported so they
can give more details.
It is also important for other people which might
see the bug in the bugtracker and want to know the resolution.
You can easily add information to a bug if you mail to
the bug-tracker mail-address and have the bug number in the subject line.
Bernhard
Hi Bernhard, Hi all,
Bernhard Reiter schrieb:
On Thu, Nov 08, 2001 at 04:54:44PM +0100, Bernhard Reiter wrote:
> So please have a look at if you have updated information enter them
> or a pointer to them into the bugtracker.
> This might be important for people who reported so they
> can give more details.
It is also important for other people which might
see the bug in the bugtracker and want to know the resolution.
You can easily add information to a bug if you mail to
the bug-tracker mail-address and have the bug number in the subject line.
I took your recommendation serious and updated all the simple cases in
the bugtracker.
But i must admit that i am unsure when to change status to resolved.
If i can not reproduce the problem, should i change to resolved? I fear
most bug reporters will not be able to answer to a bug report older than
some weeks.
cu,
Andreas
--
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
url: http://mitglied.tripod.de/AndreasLange
mail: Andreas.Lange_at_Rhein-Main.de - A.C.Lange_at_GMX.net
Hi Andreas,
On Fri, Nov 09, 2001 at 01:37:12PM +0100, Andreas Lange wrote:
Bernhard Reiter schrieb:
> On Thu, Nov 08, 2001 at 04:54:44PM +0100, Bernhard Reiter wrote:
> > So please have a look at if you have updated information enter them
> > or a pointer to them into the bugtracker.
> > This might be important for people who reported so they
> > can give more details.
I took your recommendation serious and updated all the simple cases in
the bugtracker.
Great!
This is very helpful.
But i must admit that i am unsure when to change status to resolved.
If i can not reproduce the problem, should i change to resolved? I fear
most bug reporters will not be able to answer to a bug report older than
some weeks.
A lot of bug reporter will still care.
I know because I've reported some bugs in reporting systems of
sourceforge and debian and I do still care for there resolution.
For bugs not clear enough or not reproducible I suggest we start
with the following:
First we should contact people about missing details.
If we still miss details after two weeks,
I think we should set the status of the bug to "stalled".
If it was unreproducable for another two weeks after this,
with no new details, we should call it resolved.
If we publish a new version and believe a bug to be gone
we also should contact people.
What do you think?
Also: Feel free to shift priorities around as you like so that
other developers can get a feeling which bugs are more important.
--
Professional Service around Free Software (intevation.net)
The FreeGIS Project (freegis.org)
Association for a Free Informational Infrastructure (ffii.org)
FSF Europe (fsfeurope.org)
Hi Bernhard,
Bernhard Reiter schrieb:
A lot of bug reporter will still care.
I know because I've reported some bugs in reporting systems of
sourceforge and debian and I do still care for there resolution.
For bugs not clear enough or not reproducible I suggest we start
with the following:
First we should contact people about missing details.
If we still miss details after two weeks,
I think we should set the status of the bug to "stalled".
If it was unreproducable for another two weeks after this,
with no new details, we should call it resolved.
If we publish a new version and believe a bug to be gone
we also should contact people.
What do you think?
Generally i agree. But if a bug is reported for a specific version (e.
g. pre1) that is outdated and no other person reported a similar bug i
think we should put it to resolved.
The RT is populated with some bugs which are not related to GRASS, but
to broken linux installations. I will generally help, but often it is
not possible to reproduce the bug.
Time is a very scarce ressource, so i want change to resolved.
Also: Feel free to shift priorities around as you like so that
other developers can get a feeling which bugs are more important.
This will need input from other people too.
cu,
Andreas
--
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
url: http://mitglied.tripod.de/AndreasLange
mail: Andreas.Lange_at_Rhein-Main.de - A.C.Lange_at_GMX.net
On Fri, Nov 09, 2001 at 03:05:43PM +0100, Andreas Lange wrote:
Bernhard Reiter schrieb:
> A lot of bug reporter will still care.
> I know because I've reported some bugs in reporting systems of
> sourceforge and debian and I do still care for there resolution.
>
> For bugs not clear enough or not reproducible I suggest we start
> with the following:
>
> First we should contact people about missing details.
> If we still miss details after two weeks,
> I think we should set the status of the bug to "stalled".
>
> If it was unreproducable for another two weeks after this,
> with no new details, we should call it resolved.
>
> If we publish a new version and believe a bug to be gone
> we also should contact people.
>
> What do you think?
Generally i agree. But if a bug is reported for a specific version (e.
g. pre1) that is outdated and no other person reported a similar bug i
think we should put it to resolved.
I think that at least one attempt to contact the person
is fair, we might use a shorter time period (one week?)
and then directly change it to resolved.
The RT is populated with some bugs which are not related to GRASS, but
to broken linux installations. I will generally help, but often it is
not possible to reproduce the bug.
Very true.
Time is a very scarce ressource, so i want change to resolved.
We should close bugs which are obviously not related to GRASS even sooner.
> Also: Feel free to shift priorities around as you like so that
> other developers can get a feeling which bugs are more important.
This will need input from other people too.
True, all developer have access to the bug-tracker.
If a single developer adds or substract 5 points to a value
the dialoge about the priority might start.
I believe that a resonable estimating of importance by any
developer will be better than no estimation.
Bernhard
--
Professional Service around Free Software (intevation.net)
The FreeGIS Project (freegis.org)
Association for a Free Informational Infrastructure (ffii.org)
FSF Europe (fsfeurope.org)
On Fri, Nov 09, 2001 at 05:22:27PM +0100, Bernhard Reiter wrote:
On Fri, Nov 09, 2001 at 03:05:43PM +0100, Andreas Lange wrote:
> The RT is populated with some bugs which are not related to GRASS, but
> to broken linux installations. I will generally help, but often it is
> not possible to reproduce the bug.
Very true.
> Time is a very scarce ressource, so i want change to resolved.
We should close bugs which are obviously not related to GRASS even sooner.
Another remark:
The bugtracker in fact helps us to save time as more than one person
can pick up the status of a bug and progress it.
If several bugs are seen to be related to GRASS, though they are not
it is good if people find this documented in the bugtracker
and start to search for the solution in the right places.
Bernhard