Extend the Trac Components list for GRASS

[mloskot]

I've found there are some options missing in the list of components of New Ticket form. I'd suggest to add:

• Building/Setup
• Vector support
• Raster support
• GUI (or separate component for each GUI version)

[neteler]

I have added them (some in modified form).

Markus

[martinl]

I agree, currently 'Tcl' component is used for Tcl/Tk GUI (note there is also 'Nviz' component) and 'Python' for wxGUI. Here I would suggest to rename 'Tcl' to 'Tcl/Tk GUI' and add 'wxGUI' component for wxPython-based GUI. Existing 'Python' component could be used for Python/Swig or maybe for python scripts in GRASS.

List of current components:

• Buildbot
• Database
• Docs
• Installation
• License
• NVIZ
• Python
• SWIG (all bindings)
• Tcl
• Website
• default

Martin

[martinl]

Replying to martinl:

I added new component for wxGUI and moved all the related tickets. I am not sure about renaming 'Tcl' to 'Tcl/Tk GUI'...

Martin

I agree, currently 'Tcl' component is used for Tcl/Tk GUI (note there is also 'Nviz' component) and 'Python' for wxGUI. Here I would suggest to rename 'Tcl' to 'Tcl/Tk GUI' and add 'wxGUI' component for wxPython-based GUI. Existing 'Python' component could be used for Python/Swig or maybe for python scripts in GRASS.

[hamish]

A "Platform" property would be nice too, like qgis has in their trac.

eg MSWindows/OSX/Linux/Solaris/BSD/All/Unspecified

FWIW QGIS's one breaks it down to specific linux and bsd variants as well as having an option for the general case.

​https://trac.osgeo.org/qgis/report

Hamish

[neteler]

We have to ask the QGIS people how they made this "platform" property. From the trac Webadmin interface it isn't visible. Anyone having a good contact to a QGIS trac admin?

Markus

[glynn]

Replying to hamish:

A "Platform" property would be nice too, like qgis has in their trac.

eg MSWindows/OSX/Linux/Solaris/BSD/All/Unspecified

I think that you can combine all non-Linux Unices into "Other Unix". OTOH, we might want to distinguish between Windows 2K/XP/Vista (we also need a separate entry for Cygwin, but I don't know if it matters which version of Windows Cygwin is running on). It may also be worth recording the CPU type, as there are quite a few issues which only show upon on e.g. x86-64 or OSX/PPC.

[neteler]

We have set up now (thanks to FrankW):

Platform:

MSWindows 2K|MSWindows XP|MSWindows Vista|MSWindows CygWin|MacOSX|Linux|Other Unix|All|Unspecified

Also CPU:

x86-32|x86-64|OSX/PPC|OSX/Intel|Other|All|Unspecified

Markus