[GRASS5] Dealing with old bug reports: new GRASS 6 bugtracker?

Brad Douglas rez at touchofmadness.com
Wed Aug 10 21:04:22 EDT 2005

On Wed, 2005-08-10 at 22:57 +0200, Maciek Sieczka wrote:
> I still think that CC'ing grass5 list all the messages to
> grass-bugs at intevation.de by default is a good idea. There could be an option
> not to do so if needed, but the default should be to CC in my opinion.
> Developers in charge of particular issues come and go, sprain their wrists
> ;), while any relative information should be discussed ASAP to resolve the
> proble possibly quick. Otherwise it is more likely to have 4/5 yera old
> zombie bugs like in Grass.
> Take a look at QGIS. They have all the bug discussion CCed to their dev list
> and although it is some mess in the archive, no doubt, there are positives:
> 1. folks who might never see the discussion on a particular bug report now
> can see it and share their knowledge (and learn - to be more helpfull in
> future?)
> 2. it is less likely that the same solutions are doubled
> 3. those who can't help are better informed, so they can avoid buggy actions
> and won't report same bug (or place same comments) that somebody did
> We know your opinion. What do other Folks think?

I would like to see bugs copied to the list.  I find it beneficial, but
maybe I'm the only person who runs around fixing things at random as
they come up. ;)

If the list isn't copied, add me to CC: if it isn't too much trouble.

Brad Douglas <rez at touchofmadness.com>

More information about the grass-dev mailing list