[GRASS-dev] Issue priority and labelling once in git

Veronica Andreo veroandreo at gmail.com
Sat Mar 9 11:46:30 PST 2019

Hi devs,

I just came across this issue in Qgis github:


and recalled our RFC git migration document.

I like their proposed issue labels (bug and feature request) and the
priority categories (low, medium, high). I think they are more clear-cut
than the ones proposed in our RFC document [0]; especially the priority
category. Maybe they can be combined with ours, i.e., blocker. Or what do
we put when our bug report is not critical nor blocker?

Regarding components, why not keeping raster(3d), vector, temporal. I think
those are useful and then make search easier, no? Modules is maybe too
general, IMO.

Just some comments, I'd like to hear other's (more experienced) opinions


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190309/a2312810/attachment-0001.html>

More information about the grass-dev mailing list