HEADS UP: Final call for 7.10.2 is soon

Hi *, I've just finished merging all the latest patches for GHC 7.10.2 into the STABLE branch. All in all, we've fixed a lot of bugs (over 80 tickets closed)! So, we'll probably be doing a 7.10.2 release here in a few weeks. The tentative plan was around the 14th, although it's not set in stone. (At worst, it would be pushed from the 14th to the 21st). With that in mind, if I could quickly direct your attention to the GHC bug tracker and the status page[1] - it would be really helpful if you check if the things you want are fixed! Specifically, if you want something fixed for the 7.10.2 release: - Make sure there is a ticket. It really needs to exist or we'll just forget! - If your bug is critical, please explain why! We really want to kill showstoppers ASAP, because bugs are much cheaper to fix early. If that's the case we can bump the priority if it's necessary to make things clear. - Set the milestone to 7.10.2. It'll automatically appear on the status page. That should be it - we'll be monitoring the status page regularly to keep track of new things. The current bug list is pretty small - we may move some of them out, or fix several more. So just try to let us know. As a sidenote, I'm quite happy with this release - it's fixed dozens of tricky bugs, improved some nasty corner cases in compiler performance, and overall seems like it will be high quality. Thanks to everyone who submitted patches! I'll send out another email next week as another reminder. [1] https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.10.2 -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/

Hi, bug #10009 appears on the status page with status “new”, although the bug should have been fixed in HEAD. Can this fix *please* be a part of GHC 7.10.2? At the moment, this bug breaks the incremental-computing package in a nontrivial way (and I think it breaks HList too). All the best, Wolfgang Am Dienstag, den 02.06.2015, 16:31 -0500 schrieb Austin Seipp:
Hi *,
I've just finished merging all the latest patches for GHC 7.10.2 into the STABLE branch. All in all, we've fixed a lot of bugs (over 80 tickets closed)!
So, we'll probably be doing a 7.10.2 release here in a few weeks. The tentative plan was around the 14th, although it's not set in stone. (At worst, it would be pushed from the 14th to the 21st).
With that in mind, if I could quickly direct your attention to the GHC bug tracker and the status page[1] - it would be really helpful if you check if the things you want are fixed!
Specifically, if you want something fixed for the 7.10.2 release:
- Make sure there is a ticket. It really needs to exist or we'll just forget!
- If your bug is critical, please explain why! We really want to kill showstoppers ASAP, because bugs are much cheaper to fix early. If that's the case we can bump the priority if it's necessary to make things clear.
- Set the milestone to 7.10.2. It'll automatically appear on the status page.
That should be it - we'll be monitoring the status page regularly to keep track of new things. The current bug list is pretty small - we may move some of them out, or fix several more. So just try to let us know.
As a sidenote, I'm quite happy with this release - it's fixed dozens of tricky bugs, improved some nasty corner cases in compiler performance, and overall seems like it will be high quality. Thanks to everyone who submitted patches!
I'll send out another email next week as another reminder.

On Jun 2, 2015 6:03 PM, "Wolfgang Jeltsch"
Hi,
bug #10009 appears on the status page with status “new”, although the bug should have been fixed in HEAD. Can this fix *please* be a part of GHC 7.10.2? At the moment, this bug breaks the incremental-computing package in a nontrivial way (and I think it breaks HList too).
Hlist 0.4 released a couple weeks ago works around #10009 by using FDs instead. User code isn't affected since the extra parameters are hidden by using the original TF. But that won't help if you were using those TFs with a gadt.

Please, consider my recent bug report "overlapping instances in 7.10.1" (see my resent email to this list). ------ Sergei On Tue, 2015-06-02 at 16:31 -0500, Austin Seipp wrote:
Hi *,
I've just finished merging all the latest patches for GHC 7.10.2 into the STABLE branch. All in all, we've fixed a lot of bugs (over 80 tickets closed)!
So, we'll probably be doing a 7.10.2 release here in a few weeks. The tentative plan was around the 14th, although it's not set in stone. (At worst, it would be pushed from the 14th to the 21st).
With that in mind, if I could quickly direct your attention to the GHC bug tracker and the status page[1] - it would be really helpful if you check if the things you want are fixed!
Specifically, if you want something fixed for the 7.10.2 release:
- Make sure there is a ticket. It really needs to exist or we'll just forget!
- If your bug is critical, please explain why! We really want to kill showstoppers ASAP, because bugs are much cheaper to fix early. If that's the case we can bump the priority if it's necessary to make things clear.
- Set the milestone to 7.10.2. It'll automatically appear on the status page.
That should be it - we'll be monitoring the status page regularly to keep track of new things. The current bug list is pretty small - we may move some of them out, or fix several more. So just try to let us know.
As a sidenote, I'm quite happy with this release - it's fixed dozens of tricky bugs, improved some nasty corner cases in compiler performance, and overall seems like it will be high quality. Thanks to everyone who submitted patches!
I'll send out another email next week as another reminder.

There have been some requests for a Cabal library release for 7.10.2. I
remember something about truncate directories/symbol names being an issue.
I'm CC:ing the Cabal mailing list for comments.
On Wed, Jun 3, 2015 at 3:40 PM, Sergei Meshveliani
Please, consider my recent bug report "overlapping instances in 7.10.1" (see my resent email to this list).
------ Sergei
On Tue, 2015-06-02 at 16:31 -0500, Austin Seipp wrote:
Hi *,
I've just finished merging all the latest patches for GHC 7.10.2 into the STABLE branch. All in all, we've fixed a lot of bugs (over 80 tickets closed)!
So, we'll probably be doing a 7.10.2 release here in a few weeks. The tentative plan was around the 14th, although it's not set in stone. (At worst, it would be pushed from the 14th to the 21st).
With that in mind, if I could quickly direct your attention to the GHC bug tracker and the status page[1] - it would be really helpful if you check if the things you want are fixed!
Specifically, if you want something fixed for the 7.10.2 release:
- Make sure there is a ticket. It really needs to exist or we'll just forget!
- If your bug is critical, please explain why! We really want to kill showstoppers ASAP, because bugs are much cheaper to fix early. If that's the case we can bump the priority if it's necessary to make things clear.
- Set the milestone to 7.10.2. It'll automatically appear on the status page.
That should be it - we'll be monitoring the status page regularly to keep track of new things. The current bug list is pretty small - we may move some of them out, or fix several more. So just try to let us know.
As a sidenote, I'm quite happy with this release - it's fixed dozens of tricky bugs, improved some nasty corner cases in compiler performance, and overall seems like it will be high quality. Thanks to everyone who submitted patches!
I'll send out another email next week as another reminder.
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
participants (5)
-
adam vogt
-
Austin Seipp
-
Johan Tibell
-
Sergei Meshveliani
-
Wolfgang Jeltsch