[GHC DevOps Group] The future of Phabricator

[Carter Schonwald]

For what it’s worth, I’ve never found phab / arc to be the bottle neck /
actual time consuming piece of doing anything for ghc

It’s defintely the nicest code review substrate I’ve engaged with

One question I have : how does the llvm org manage / handle their
phabricator instance and or ci substrate. Maybe they have wisdom that can
help ?

On Thu, Nov 1, 2018 at 7:27 PM Vladislav Zavialov <vladislav at serokell.io>
wrote:

> To put my 2¢ – I will be happy with whatever service provides the most
> reliable CI.
>
> In terms of workflow, I like Ben's suggestion:
>
>   * Consider a PR to be a stack of differentials, with each commit
> being an atomic change in that stack.
> _______________________________________________
> 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-devops-group/attachments/20181101/4e8c9fdd/attachment.html>