Hi, po 6. 5. 2019 v 22:49 odesÃlatel Markus Neteler <nete...@osgeo.org> napsal: > Why wait for that with the source code migration? > Please let's start with it. The tickets can follow in a second step. > This also prevents us from being overloaded.
my idea to do migration in one step comes from assumption that new git commits can be referenced to github issues. Issue migration needs to be also done on private repository. This would require to set up empty private repo, migrate tickets and than transfer ticket using GitHub API to public repo. This complicates procedure a bit. I would still prefer to do source code and issues migration together even it will take some time. Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev