more releases

Bardur Arantsson spam at
Mon Sep 7 16:05:56 UTC 2015

On 09/07/2015 04:57 PM, Simon Peyton Jones wrote:
> Merging and releasing a fix to the stable branch always carries a cost:
> it might break something else.  There is a real cost to merging, which
> is why we've followed the lazy strategy that Ben describes.

A valid point, but the upside is that it's a very fast operation to
revert if a release is "bad"... and get that updated release into the wild.


More information about the ghc-devs mailing list