Moving Haddock *development* out of GHC tree

[Johan Tibell]

On Fri, Aug 8, 2014 at 10:11 AM, Simon Peyton Jones <simonpj at microsoft.com>
wrote:

>   The biggest disadvantage in my mind is that you're setting yourself up
> for a potentially huge merge just before the GHC release and might block
> the GHC release until that merge is done (assuming that haddock is still
> shipped with GHC).
>
>
>
> Excellent point.
>
>
>
> The merge shouldn’t block the release, though. In extremis, I guess we
> could always release the GHC fork of Haddock if the tip of Haddock wasn’t
> merged to match GHC!  But I doubt it’ll come to that
>

But as you mentioned the GHC fork of Haddock might not work (it might just
type check) so at the very least Mateusz is signing up for validating that
it indeed works before a GHC release. That's of course fine, I just want
people to understand what we're signing up for.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20140808/675c98bd/attachment.html>