[Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Phyx]

Can they be sent from a different email address than the main.
Gitlab+margebot are quite. Ahum, noisy.. and filtering based on message
content has a potential for false positives.

Kind regards,
Tamar

On Wed, Mar 6, 2019, 12:33 Matthew Pickering <matthewtpickering at gmail.com>
wrote:

> I think gitlab can be configured so notifications are sent for new issues
> and comments on issues which should achieve the same thing as the mailing
> list did?
>
>
>
> On Wed, Mar 6, 2019 at 12:00 PM Sylvain Henry <sylvain at haskus.fr> wrote:
>
>> I use it to track tickets and I would also like to see it continued.
>>
>> Sylvain
>>
>> On 06/03/2019 12:33, Ara Adkins wrote:
>> > Personally I would like to see it continued, but it may not be worth
>> the work if I’m in a minority here.
>> >
>> > A potential stopgap would be to ‘watch’ the GHC project on our gitlab
>> instance, but I can’t see any way to decide to get emails for notifications
>> rather than having to check in at GitLab all the time.
>> >
>> > _ara
>> >
>> >> On 6 Mar 2019, at 11:21, Ben Gamari <ben at well-typed.com> wrote:
>> >>
>> >>
>> >>
>> >>> On March 6, 2019 6:11:49 AM EST, Ara Adkins <me at ara.io> wrote:
>> >>> Super excited for this! Thank you to everyone whose put in so much
>> hard
>> >>> work to get it done!
>> >>>
>> >>> One question: what is happening with the trac tickets mailing list? I
>> >>> imagine it’ll be going away, but for those of us that use it to keep
>> >>> track of things is there a recommended alternative?
>> >>>
>> >> The ghc-commits list will continue to work.
>> >>
>> >> The ghc-tickets list is a good question. I suspect that under gitlab
>> there will be less need for this list but we may still want to continue
>> maintaining it regardless for continuity's sake. Thoughts?
>> >>
>> >> Cheers,
>> >>
>> >> - Ben
>> >>
>> >>
>> >>
>> >>> Best,
>> >>> _ara
>> >>>
>> >>>> On 6 Mar 2019, at 01:21, Ben Gamari <ben at well-typed.com> wrote:
>> >>>>
>> >>>> Hi everyone,
>> >>>>
>> >>>> Over the past few weeks we have been hard at work sorting out the
>> >>>> last batch of issues in GHC's Trac-to-GitLab import [1]. At this
>> >>> point I
>> >>>> believe we have sorted out the issues which are necessary to perform
>> >>> the
>> >>>> final migration:
>> >>>>
>> >>>> * We are missing only two tickets (#1436 and #2074 which will require
>> >>> a
>> >>>>   bit of manual intervention to import due to extremely large
>> >>>>   description lengths)
>> >>>>
>> >>>> * A variety of markup issues have been resolved
>> >>>>
>> >>>> * More metadata is now preserved via labels. We may choose to
>> >>>>   reorganize or eliminate some of these labels in time but it's
>> >>> easier
>> >>>>   to remove metadata after import than it is to reintroduce it. The
>> >>>>   logic which maps Trac metadata to GitLab labels can be found here
>> >>> [2]
>> >>>> * We now generate a Wiki table of contents [3] which is significantly
>> >>>>   more readable than GitLab's default page list. This will be updated
>> >>>>   by a cron job until underlying GitLab pages list becomes more
>> >>>>   readable.
>> >>>>
>> >>>> * We now generate redirects for Trac ticket and Wiki links (although
>> >>>>   this isn't visible in the staging instance)
>> >>>>
>> >>>> * Milestones are now properly closed when closed in Trac
>> >>>>
>> >>>> * Mapping between Trac and GitLab usernames is now a bit more robust
>> >>>>
>> >>>> As in previous test imports, we would appreciate it if you could have
>> >>> a
>> >>>> look over the import and let us know of any problems your encounter.
>> >>>>
>> >>>> If no serious issues are identified with the staging site we plan to
>> >>>> proceed with the migration this coming weekend. The current migration
>> >>>> plan is to perform the final import on gitlab.haskell.org on
>> >>> Saturday, 9
>> >>>> March 2019.
>> >>>>
>> >>>> This will involve both gitlab.haskell.org and ghc.haskell.org being
>> >>> down
>> >>>> for likely the entirety of the day Saturday and likely some of Sunday
>> >>>> (EST time zone). Read-only access will be available to
>> >>>> gitlab.staging.haskell.org for ticket lookup while the import is
>> >>>> underway.
>> >>>>
>> >>>> After the import we will wait at least a week or so before we begin
>> >>> the
>> >>>> process of decommissioning Trac, which will be kept in read-only mode
>> >>>> for the duration.
>> >>>>
>> >>>> Do let me know if the 9 March timing is problematic.
>> >>>>
>> >>>> Cheers,
>> >>>>
>> >>>> - Ben
>> >>>>
>> >>>>
>> >>>> [1] https://gitlab.staging.haskell.org/ghc/ghc
>> >>>> [2]
>> >>>
>> https://github.com/bgamari/trac-to-remarkup/blob/master/TicketImport.hs#L227
>> >>>> [3] https://gitlab.staging.haskell.org/ghc/ghc/wikis/index
>> >>>> _______________________________________________
>> >>>> Haskell-Cafe mailing list
>> >>>> To (un)subscribe, modify options or view archives go to:
>> >>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
>> >>>> Only members subscribed via the mailman list are allowed to post.
>> >> --
>> >> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>> > _______________________________________________
>> > ghc-devs mailing list
>> > ghc-devs at haskell.org
>> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>> _______________________________________________
>> ghc-devs mailing list
>> ghc-devs at haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20190306/89919e92/attachment.html>