Re: [RFC] switch to GitLab / gitlab.com

[Jonas Hahnfeld]

Am Montag, den 10.02.2020, 09:20 +0100 schrieb Jonas Hahnfeld:
> 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.

So I eventually convinced my script to migrate close to all issues [1],
and all references to other issues that I checked so far are now
working. Could you maybe check again and let me know if something's
still broken? In any case I've already modified my script to first sort
the issues and not take the (random?) order from SF.

Jonas

1: except for #2965, #2044, #2765, #1939, #3654, #4778, #887, #162,
#328, #689, #1181, #1618, #1854 - these were considered "spam" but this
can be easily worked around by making the repo private for the course
of the migration.

signature.asc
Description: This is a digitally signed message part