migrate trac issues to github

[martinl]

This issue is open for discussion. Note that any kind of migration hasn't been yet decided by GRASS PSC. See also related #3722.

Code used for migration source:grass-addons/tools/svn2git/trac2github.php​

Links below point to a first attempt, only issues with milestone set to 8.0.0 have been migrated in order to allow first public review.

Features:

• migrate milestone, ​https://github.com/grass-svn2git/grass-issues-test/milestones
• migrate labels, ​https://github.com/grass-svn2git/grass-issues-test/labels
  • labels are re-organized, see ​https://trac.osgeo.org/grass/browser/grass-addons/tools/svn2git/trac2github.cfg#L97
• tickets, ​https://github.com/grass-svn2git/grass-issues-test/issues
  • trac wiki, source, attachment, images should be remap to URL pointing to trac instance
  • authors linked to github accounts, ​https://trac.osgeo.org/grass/browser/grass-addons/tools/svn2git/trac2github.cfg#L19
  • links to closed issues point to trac instance
  • links to open issues remapped to github
  • revision links remapped to URL (​https://trac.osgeo.org/grass/changeset)
  • trac G7 (and similar tags) remapped to URL

PLEASE HELP WITH REVIEWING this draft migration (tickets, labels reorgranization, check if your github account is properly linked in ​https://trac.osgeo.org/grass/browser/grass-addons/tools/svn2git/trac2github.cfg#L19)

[martinl]

Bearing in mind that probably only G7+ issues will be migrated, it's still a big number:

8.0.0+7.8.0+7.6.1+7.4.5+7.2.4+7.0.7

42+32+325+48+144+163 -> 754

PLEASE HELP TO REDUCE NUMBER OF OPEN ISSUES! Some of them are outdated, probably already fixed... Public review is very welcome, thanks!

BTW, we should probably start marking older releases by EndOfLife term to be clear than no other releases are planned. What about keeping only two last release branches active. So:

• 7.6.1 planned
• 7.4.5 planned
• 7.2 EOL (no 7.4.5 is planned)
• 7.0 EOL (no 7.0.7 is planned)

Then we could change milestone of all EOL tickets to 7.6.1. (or 7.6.2)

This should be done ideally before migration.

[neteler]

Replying to martinl:

PLEASE HELP TO REDUCE NUMBER OF OPEN ISSUES! Some of them are outdated, probably already fixed... Public review is very welcome, thanks!

+1! Don't be shy, please check the open bug reports here.

BTW, we should probably start marking older releases by EndOfLife term to be clear than no other releases are planned. What about keeping only two last release branches active. So:

• 7.6.1 planned
• 7.4.5 planned
• 7.2 EOL (no 7.4.5 is planned)
• 7.0 EOL (no 7.0.7 is planned)

Then we could change milestone of all EOL tickets to 7.6.1. (or 7.6.2)

This should be done ideally before migration.

Also +1. To declare EOL is fairly common.

[neteler]

@all: still some work to be done (big thanks to Martin Landa to clean up so many tickets these days!):

• ​https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=7.0.7
• ​https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=7.2.4

... not sure if they must be reduced to exactly 0 open bugs/wishes prior to GitHub migration but still some relevant bug reports may wait for us in these two lists. Please update them, along with incrementing the milestone to >= 7.4. Thanks!

[neteler]

Migration of the issue management has been concluded earlier this year.

Open trac bugs will be managed here while new bugs are reported and being worked on here: ​https://github.com/OSGeo/grass/issues

Closing.