[GRASS-PSC] git migration
Vaclav Petras
wenzeslaus at gmail.com
Sat Apr 20 06:35:13 PDT 2019
On Thu, Apr 11, 2019 at 4:40 PM Markus Neteler <neteler at osgeo.org> wrote:
> On Wed, Apr 10, 2019 at 4:58 PM Vaclav Petras <wenzeslaus at gmail.com>
> wrote:
> > On Sun, Apr 7, 2019 at 4:02 PM Markus Neteler <neteler at osgeo.org> wrote:
> >>
> >>
> >> RFC 6: Migration from SVN to GitHub
> >> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
> >
> > Looks great. Thanks!
> >
> > One thing it lacks are best practices for using Git. Git is not
> Subversion and we just can't use it as Subversion.
>
> Please suggest a text snippet to add there (or add directly).
>
Added.
> >> It also proposes an exit strategy incl. to implement a
> >> continuous mirror on GitLab.com.
> >
> > How realistic is the continuous mirror? I know GitLab has migration
> tools, but does it have sync as well?
>
> https://docs.gitlab.com/ee/workflow/repository_mirroring.html
> "
> Repository mirroring allows for mirroring of repositories to and from
> external sources. It can be used to mirror branches, tags, and commits
> between repositories.
> A repository mirror at GitLab will be updated automatically. You can
> also manually trigger an update at most once every 5 minutes.
> "
>
> ... looks fine.
>
The mirroring covers only the code, but not the issues which we are also
migrating. The migration does cover them, but the problem is the guarantee
of being able to do the migration when needed. A periodical backup from
GitHub would be probably fine.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-psc/attachments/20190420/7378a780/attachment.html>
More information about the grass-psc
mailing list