Re: Request for comments on dry-run Trac -> GitLab migration

2019-02-05 Thread Julian Leviston
> On 5 Feb 2019, at 3:06 am, Ben Gamari wrote: > > TL;DR. Have a look at this [2] test import of GHC's Trac tickets. Tell us > what issues you find. > First up, it’s utterly amazing to me that this is importable and with all links transferred and syntax highlighting and whatnot! so

Re: Request for comments on dry-run Trac -> GitLab migration

2019-02-04 Thread Niklas Hambüchen
On 05/02/2019 4:49 AM, Ben Gamari wrote:> Yes, this is the cause and the import does handle this; I just (yet again) forgot to rerun this stage of the import. This should be fixed now. For me, nothing seems to have changed on https://gitlab.staging.haskell.org/ghc/ghc/issues/13497

Re: Request for comments on dry-run Trac -> GitLab migration

2019-02-04 Thread Ben Gamari
Niklas Hambüchen writes: > I find that commits aren't mentioned on the corresponding issues, for example > there's no equivalent of > > https://ghc.haskell.org/trac/ghc/ticket/13497#comment:27 > > on > > https://gitlab.staging.haskell.org/ghc/ghc/issues/13497 > > I vaguely remember

Re: Request for comments on dry-run Trac -> GitLab migration

2019-02-04 Thread Niklas Hambüchen
I find that commits aren't mentioned on the corresponding issues, for example there's no equivalent of https://ghc.haskell.org/trac/ghc/ticket/13497#comment:27 on https://gitlab.staging.haskell.org/ghc/ghc/issues/13497 I vaguely remember these "commit posts" being discussed before

RE: Request for comments on dry-run Trac -> GitLab migration

2019-02-04 Thread Ben Gamari
Simon Peyton Jones via ghc-devs writes: > Could we arrange that searching for the ticket number succeeds? > Eg searching for 12088 fails, and 16013. > Yes, this is a bug [1]. I will bring it up with David. Cheers, - Ben [1] https://gitlab.com/gitlab-org/gitlab-ce/issues/30974 signature.asc

Re: Request for comments on dry-run Trac -> GitLab migration

2019-02-04 Thread Ryan Scott
There appears to be some impedance mismatches between GitLab's formatting and Trac's formatting in certain places. For example, see the bottom of this issue [1], which has a long, hyperlinked line with the phrase:

Re: Request for comments on dry-run Trac -> GitLab migration

2019-02-04 Thread Matthew Pickering
There is this other issue though which explains that searching in the issues view for a ticket number does fail. https://gitlab.com/gitlab-org/gitlab-ce/issues/30974 https://gitlab.staging.haskell.org/ghc/ghc/issues?scope=all=%E2%9C%93=opened=%231234 So if you want to search for a ticket by

Re: Request for comments on dry-run Trac -> GitLab migration

2019-02-04 Thread Matthew Pickering
Thanks Ben, looks amazing. I don't think the trac metadata boxes should always be visible. They are unobtrusive now and tbh, I don't think I will be opening them up much when looking at tickets. Simon, I think if you start the query with a # then it "works". For example, search for #12088

RE: Request for comments on dry-run Trac -> GitLab migration

2019-02-04 Thread Simon Peyton Jones via ghc-devs
: Request for comments on dry-run Trac -> GitLab migration | | TL;DR. Have a look at this [2] test import of GHC's Trac tickets. Tell us | what issues you find. | | | Hello everyone, | | As you likely know, we are currently in the process of consolidating | GHC's infrastruct

Request for comments on dry-run Trac -> GitLab migration

2019-02-04 Thread Ben Gamari
TL;DR. Have a look at this [2] test import of GHC's Trac tickets. Tell us what issues you find. Hello everyone, As you likely know, we are currently in the process of consolidating GHC's infrastructure on GitLab [1]. The last step of this process is to migrate our tickets and wiki from