[GRASS-dev] GRASS at GForge first steps
tutey at o2.pl
Sun Nov 19 15:06:16 EST 2006
Maciej Sieczka wrote:
> Dear Developers,
> What "GRASS components" tags would you propose to be added in the "code
> issues tracker
> http://wald.intevation.org/tracker/?atid=182&group_id=21&func=browse ?
> (click "Submit New" and see the tags in the "GRASS component:" field)
> What libraries? Other stuff? I don't know GRASS good enough and I'm not
> a programmer.
How about adding a "module/library" select box tag, which would have 2
choices: "module" and "library". Such tag, in conjuction with "GRASS
component", would indicate whether the nature of a given issue lies in
a module, or in some underlying library.
"GRASS component"=raster and "module/library"=module
means the issue is in some raster library
"GRASS component"=vector and "module/library"=library
means a bug in some vector library
This should let us have the module and library issues somewhat
separated in the tracker, while not overloading the tracker with many
specific library names to choose from, when reporting an issue/managing it.
More information about the grass-dev