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

[Nikos Alexandris]

* Nikos Alexandris <nik at nikosalexandris.net> [2019-03-10 21:46:14 +0100]:

>* Markus Neteler <neteler at osgeo.org> [2019-03-10 21:29:12 +0100]:
>
>>Hi all,
>>
>>On Sat, Mar 9, 2019 at 8:46 PM Veronica Andreo <veroandreo at gmail.com> wrote:
>>>
>>>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.
>>
>>The current draft proposal can now be seen here:
>>
>>https://github.com/grass-svn2git/grass-issues-test/issues
>>
>>>Just some comments, I'd like to hear other's (more experienced) opinions
>>
>>Yes, a (timely) discussion is welcome.
>
>Labeling is cool. Don't forget though that most git repository hosting
>services, provide for "boards" or similar. It's an extremely useful way
>to organise, to read over what is what to do and who's doing what.
>This by itself, is a major advantage to move on with modern "git"
>web-services.

https://github.com/grass-svn2git/grass-issues-test/projects

Nikos