
Hi *, (This is an email primarily aimed at users reading this list and developers who have any interest). As some of you may know, there's currently a 7.10.3 milestone and status page on our wiki: https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.10.3 The basic summary is best captured on the above page: "We have not yet decided when, or even whether, to release GHC 7.10.3. We will do so if (but only if!) we have documented cases of "show-stoppers" in 7.10.2. Namely, cases from users where - You are unable to use 7.10.2 because of some bug - There is no reasonable workaround, so you are truly stuck - We know how to fix it - The fix is not too disruptive; i.e. does not risk introducing a raft of new bugs" That is, we're currently not fully sold on the need for a release. However, the milestone and issue page serve as a useful guide, and also make it easier to keep track of smaller, point-release worthy issues. So in the wake of the 8.0 roadmap I just sent: If you *need* 7.10.3 because the 7.10.x series has a major regression or problem you can't work around, let us know! - Find or file a bug in Trac - Make sure it's highest priority - Assign it to the 7.10.3 milestone - Follow up on this email if possible, or edit it on the status page text above - it would be nice to get some public feedback in one place about what everyone needs. Currently we have two bugs on the listed page in the 'show stopper category', possibly the same bug, which is a deal-breaker for HERMIT I believe. Knowing of anything else would be very useful. Thanks all! -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/

On Mon, Sep 14, 2015 at 3:53 PM, Austin Seipp wrote:
Hi *,
(This is an email primarily aimed at users reading this list and developers who have any interest).
As some of you may know, there's currently a 7.10.3 milestone and status page on our wiki:
https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.10.3
The basic summary is best captured on the above page:
"We have not yet decided when, or even whether, to release GHC 7.10.3. We will do so if (but only if!) we have documented cases of "show-stoppers" in 7.10.2. Namely, cases from users where
- You are unable to use 7.10.2 because of some bug - There is no reasonable workaround, so you are truly stuck - We know how to fix it - The fix is not too disruptive; i.e. does not risk introducing a raft of new bugs"
That is, we're currently not fully sold on the need for a release. However, the milestone and issue page serve as a useful guide, and also make it easier to keep track of smaller, point-release worthy issues.
So in the wake of the 8.0 roadmap I just sent: If you *need* 7.10.3 because the 7.10.x series has a major regression or problem you can't work around, let us know!
- Find or file a bug in Trac - Make sure it's highest priority - Assign it to the 7.10.3 milestone - Follow up on this email if possible, or edit it on the status page text above - it would be nice to get some public feedback in one place about what everyone needs.
Currently we have two bugs on the listed page in the 'show stopper category', possibly the same bug, which is a deal-breaker for HERMIT I believe. Knowing of anything else would be very useful.
Would tracking down and fixing some of the reported time and space regressions qualify as 7.10.3 material?

My two showstoppers are https://ghc.haskell.org/trac/ghc/ticket/10568 and
https://ghc.haskell.org/trac/ghc/ticket/10672, both of which seem to be
already on track for 7.10.3, great!
On Mon, Sep 14, 2015 at 7:15 AM, Tuncer Ayaz
On Mon, Sep 14, 2015 at 3:53 PM, Austin Seipp wrote:
Hi *,
(This is an email primarily aimed at users reading this list and developers who have any interest).
As some of you may know, there's currently a 7.10.3 milestone and status page on our wiki:
https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.10.3
The basic summary is best captured on the above page:
"We have not yet decided when, or even whether, to release GHC 7.10.3. We will do so if (but only if!) we have documented cases of "show-stoppers" in 7.10.2. Namely, cases from users where
- You are unable to use 7.10.2 because of some bug - There is no reasonable workaround, so you are truly stuck - We know how to fix it - The fix is not too disruptive; i.e. does not risk introducing a raft of new bugs"
That is, we're currently not fully sold on the need for a release. However, the milestone and issue page serve as a useful guide, and also make it easier to keep track of smaller, point-release worthy issues.
So in the wake of the 8.0 roadmap I just sent: If you *need* 7.10.3 because the 7.10.x series has a major regression or problem you can't work around, let us know!
- Find or file a bug in Trac - Make sure it's highest priority - Assign it to the 7.10.3 milestone - Follow up on this email if possible, or edit it on the status page text above - it would be nice to get some public feedback in one place about what everyone needs.
Currently we have two bugs on the listed page in the 'show stopper category', possibly the same bug, which is a deal-breaker for HERMIT I believe. Knowing of anything else would be very useful.
Would tracking down and fixing some of the reported time and space regressions qualify as 7.10.3 material? _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Oh, and I guess it was implied, but I'm hugely in favor of a release : )
#10568 breaks linking with GLFW on Mac, and #10672 breaks linking with C++
libraries on Windows (Bullet Physics, in this case).
We're working on and evangelizing Haskell for game and VR dev heavily right
now and those are both directly in the critical path.
Cheers
Luke
On Mon, Sep 14, 2015 at 3:21 PM, Luke Iannini
My two showstoppers are https://ghc.haskell.org/trac/ghc/ticket/10568 and https://ghc.haskell.org/trac/ghc/ticket/10672, both of which seem to be already on track for 7.10.3, great!
On Mon, Sep 14, 2015 at 7:15 AM, Tuncer Ayaz
wrote: On Mon, Sep 14, 2015 at 3:53 PM, Austin Seipp wrote:
Hi *,
(This is an email primarily aimed at users reading this list and developers who have any interest).
As some of you may know, there's currently a 7.10.3 milestone and status page on our wiki:
https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.10.3
The basic summary is best captured on the above page:
"We have not yet decided when, or even whether, to release GHC 7.10.3. We will do so if (but only if!) we have documented cases of "show-stoppers" in 7.10.2. Namely, cases from users where
- You are unable to use 7.10.2 because of some bug - There is no reasonable workaround, so you are truly stuck - We know how to fix it - The fix is not too disruptive; i.e. does not risk introducing a raft of new bugs"
That is, we're currently not fully sold on the need for a release. However, the milestone and issue page serve as a useful guide, and also make it easier to keep track of smaller, point-release worthy issues.
So in the wake of the 8.0 roadmap I just sent: If you *need* 7.10.3 because the 7.10.x series has a major regression or problem you can't work around, let us know!
- Find or file a bug in Trac - Make sure it's highest priority - Assign it to the 7.10.3 milestone - Follow up on this email if possible, or edit it on the status page text above - it would be nice to get some public feedback in one place about what everyone needs.
Currently we have two bugs on the listed page in the 'show stopper category', possibly the same bug, which is a deal-breaker for HERMIT I believe. Knowing of anything else would be very useful.
Would tracking down and fixing some of the reported time and space regressions qualify as 7.10.3 material? _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

As you mentioned, the two show stoppers for HERMIT are #10528
(specifically SPJs commit in comment:15 - see [1]) and #10829 (see
D1246). The first disables inlining/rule application in the LHS of
rules, the second does the same in the RHS. nofib results for the
latter are on the ticket.
I've set both to 7.10.3 milestone and high priority... thanks for merging them!
[1] bc4b64ca5b99bff6b3d5051b57cb2bc52bd4c841
On Mon, Sep 14, 2015 at 6:53 AM, Austin Seipp
Hi *,
(This is an email primarily aimed at users reading this list and developers who have any interest).
As some of you may know, there's currently a 7.10.3 milestone and status page on our wiki:
https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.10.3
The basic summary is best captured on the above page:
"We have not yet decided when, or even whether, to release GHC 7.10.3. We will do so if (but only if!) we have documented cases of "show-stoppers" in 7.10.2. Namely, cases from users where
- You are unable to use 7.10.2 because of some bug - There is no reasonable workaround, so you are truly stuck - We know how to fix it - The fix is not too disruptive; i.e. does not risk introducing a raft of new bugs"
That is, we're currently not fully sold on the need for a release. However, the milestone and issue page serve as a useful guide, and also make it easier to keep track of smaller, point-release worthy issues.
So in the wake of the 8.0 roadmap I just sent: If you *need* 7.10.3 because the 7.10.x series has a major regression or problem you can't work around, let us know!
- Find or file a bug in Trac - Make sure it's highest priority - Assign it to the 7.10.3 milestone - Follow up on this email if possible, or edit it on the status page text above - it would be nice to get some public feedback in one place about what everyone needs.
Currently we have two bugs on the listed page in the 'show stopper category', possibly the same bug, which is a deal-breaker for HERMIT I believe. Knowing of anything else would be very useful.
Thanks all!
-- Regards,
Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/ _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users

Building Haddock documentation on Windows for larger packages (e.g. OpenGLRaw) is broken in 7.10.2, similar to linking: The reason is once again the silly Windows command line length limitation, so we need response files here, too. Haddock 2.16.1 already has support for this, but this seems to be broken (probably https://github.com/haskell/haddock/commit/9affe8f6b3a9b07367c8c14162aecea8b1... is missing), see the corresponding check in cabal ( https://github.com/haskell/cabal/blob/master/Cabal/Distribution/Simple/Haddo... ). So in a nutshell: We would need a new Haddock release (bundled with GHC 7.10.3) and a new cabal release with support for Haddock response files (in cabal's HEAD, but not yet released). Would this be possible?
participants (5)
-
Andrew Farmer
-
Austin Seipp
-
Luke Iannini
-
Sven Panne
-
Tuncer Ayaz