[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC] switch to GitLab / gitlab.com
From: |
Jonas Hahnfeld |
Subject: |
Re: [RFC] switch to GitLab / gitlab.com |
Date: |
Mon, 10 Feb 2020 09:20:32 +0100 |
User-agent: |
Evolution 3.34.3 |
Am Sonntag, den 09.02.2020, 23:34 +0100 schrieb Federico Bruni:
> Il giorno dom 9 feb 2020 alle 22:50, Jonas Hahnfeld <
> address@hidden
> >
> ha scritto:
> > Thanks for sharing! I put together a simplistic script to create a
> > proof-of-concept:
> > https://gitlab.com/lilypond-issues/lilypond/issues
> >
> >
> > It's only 1137 issues (now my server is blacklisted for spamming...),
> > but it has some important features mentioned so far:
> > * It preserves the issue numbers, and additionally has a link to SF.
> > * It migrates the current description and all comments.
> > * It copies the attachments and adds links / previews.
> > * Status, Type, and Priority are migrated as labels.
> > * The migrated issue is closed when it was closed on SF.
> >
> > Obviously I can't post in other person's names, so it has "Originally
> > reported / posted by" lines at the beginning of every issue and
> > comment
> > (unless it had already been migrated from Google Code). Another
> > shortcoming is that I could not reproduce the threaded structure on
> > SF,
> > so all comments are sorted chronologically.
> >
> > Please all take a look and let me know what you think!
>
> Pretty impressive! I gave a quick glance and it looks great.
> I suggest you eventually share the script in the gitlab.com issue I
> linked before so others can use it...
Will do, probably put it in a public repository (possibly even below
the lilypond group), just for archival purposes.
> Another shortcoming is that links to other issues are broken
> (transformed in links to non-existing anchors in current issue).
I think that is because some issues have not (yet) been migrated. I
hope these links start to work once all is there.
> When I tested the Google Code>GitHub issue migration years ago, I was
> blocked by Github filters and I had to ask a special permission to
> continue. In case you see a block try contacting GitLab.com.
For now it was only the text of a single issue that was considered
"spam". But I'll keep that in mind, maybe ask for the final migration
if I hit more problems in the tests.
Jonas
signature.asc
Description: This is a digitally signed message part
- Re: [RFC] switch to GitLab / gitlab.com, (continued)
- Re: [RFC] switch to GitLab / gitlab.com, Federico Bruni, 2020/02/07
- Re: [RFC] switch to GitLab / gitlab.com, Federico Bruni, 2020/02/07
- Re: [RFC] switch to GitLab / gitlab.com, Jonas Hahnfeld, 2020/02/09
- Re: [RFC] switch to GitLab / gitlab.com, David Kastrup, 2020/02/09
- Re: [RFC] switch to GitLab / gitlab.com, Werner LEMBERG, 2020/02/09
- Re: [RFC] switch to GitLab / gitlab.com, Jonas Hahnfeld, 2020/02/09
- Re: [RFC] switch to GitLab / gitlab.com, Jonas Hahnfeld, 2020/02/09
- Re: [RFC] switch to GitLab / gitlab.com, Federico Bruni, 2020/02/09
- Re: [RFC] switch to GitLab / gitlab.com, Han-Wen Nienhuys, 2020/02/10
- Re: [RFC] switch to GitLab / gitlab.com, Jonas Hahnfeld, 2020/02/10
- Re: [RFC] switch to GitLab / gitlab.com,
Jonas Hahnfeld <=
- Re: [RFC] switch to GitLab / gitlab.com, Jonas Hahnfeld, 2020/02/11
- Re: [RFC] switch to GitLab / gitlab.com, Federico Bruni, 2020/02/11
- Re: [RFC] switch to GitLab / gitlab.com, Jonas Hahnfeld, 2020/02/11
- Re: [RFC] switch to GitLab / gitlab.com, David Kastrup, 2020/02/11
- Re: [RFC] switch to GitLab / gitlab.com, Jonas Hahnfeld, 2020/02/11
- Re: [RFC] switch to GitLab / gitlab.com, David Kastrup, 2020/02/11
- Re: [RFC] switch to GitLab / gitlab.com, Jonas Hahnfeld, 2020/02/11
- Re: [RFC] switch to GitLab / gitlab.com, David Kastrup, 2020/02/11
- Re: [RFC] switch to GitLab / gitlab.com, Jonas Hahnfeld, 2020/02/11
- Re: [RFC] switch to GitLab / gitlab.com, David Kastrup, 2020/02/11