[GRASS-dev] svn/trac -> git/github migration plan

[Markus Neteler]

On Fri, May 10, 2019 at 5:06 PM Martin Landa <landa.martin at gmail.com> wrote:
>
> Hi,
>
> út 7. 5. 2019 v 10:26 odesílatel Martin Landa <landa.martin at gmail.com> napsal:
> > 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.
>
> back to this topic, I added to trac an alternative scenario based on
> two steps (source code and issues migration separated) [1]. Opinions
> welcome. We are very close to day D.

Excellent.

IMHO the separate migration of source code and issues is the way to go.
Like that we can already work with the then completed migration next
weekend in Berlin and define workflows.

Issue migration can follow then.

Best,
Markus

> Ma
>
> [1] https://trac.osgeo.org/grass/wiki/GitMigration#Scenario2twosteps