Re: [trial] current status

[Étienne Beaulé]

A little consideration to take in account is how comments are numbered in tasks 
in Sourceforge. If they are directly imported, the comment numbers will become 
task links and would spam the tasks with those numbers.

Étienne

> Le 3 mai 2020 à 08:00, Jonas Hahnfeld <address@hidden> a écrit :
> 
> Hi all,
> 
> for those not following very closely, a few updates for GitLab:
> 1) We now have access over https://gitlab.com/lilypond, thanks Jan!
> 2) There's a webhook that automatically (re)sets the patch status when
> opening a MR or pushing new commits. It's currently on my server (which
> makes it easy for me to experiment), but I'm open to putting this on
> lilypond.org eventually. Not a blocker for the migration though.
> 3) I wrote a small script to track the status of all patches for James'
> countdown emails. The same information is already available in the list
> of all merge requests, but not easily pasteable as text.
> 
> As the last two points involve some (short) scripts and I already have
> two more for the migration, I'd like to put them into a new repository;
> maybe https://gitlab.com/lilypond/infrastructure ? (I think they're
> sufficiently orthogonal to LilyPond itself that they deserve their own
> place to live.)
> 
> Other than that, Trevor mentioned that the migration script creates
> very many labels, in the order of 600. Most of them are "Fixed_x_y_z"
> (or variations). I propose to transform them into milestones which can
> be closed and are the GitLab way of grouping issues and patches
> contained in a release. This is likely a semi-manual process that I
> volunteer to handle after the final migration.
> 
> Thoughts or other observations that would block us from using GitLab?
> 
> Jonas