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

[Veronica Andreo]

Hi devs,

I just came across this issue in Qgis github:

https://github.com/qgis/QGIS-Enhancement-Proposals/issues/141

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

Cheers,
Vero

[0]
https://trac.osgeo.org/grass/wiki/PSC/RFC/6_MigrationGitHub#ActivatingtheGitHubissuetracker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190309/a2312810/attachment-0001.html>