Tentative high-level plans for 7.10.1
johan.tibell at gmail.com
Tue Oct 7 09:23:32 UTC 2014
On Tue, Oct 7, 2014 at 10:12 AM, Simon Peyton Jones <simonpj at microsoft.com>
> | 8960 looks rather serious and potentially makes all of 7.8 a no-go
> | for some users.
I think this is the big issue. If you look at all the related bugs linked
from #8960, lots of users are affected. I think this bug alone probably
warrants a release. We should also move all those related bugs to the 7.8.4
milestone, so the impact of this issue is more clear.
> My conclusion
> * I think we (collectively!) should make a serious attempt to fix
> bugs on a major release branch. (I agree that upgrading to the next
> release often simply brings in a new wave of bugs because of GHC's
> rapid development culture.)
> * We can only possibly do this if
> a) we can distinguish "show-stopping" from "nice to have"
> b) we get some help (thank you John Lato for implicitly offering)
All sounds good to me. I can help with backporting bug fixes if needed. In
return I would encourage people to not mix bug fixes with "I rewrote the
compiler" commits. :)
I would define a "show-stopping" bug as one that simply prevents you from
> using the release altogether, or imposes a very large cost at the user end.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghc-devs