Hi all, This is just a quick summary of our plans for GHC 6.10.2. While it is possible that we will fix some others, for the 6.10.2 release we mainly intend to look at the high-priority bugs in the 6.10.2 milestone. They are listed here: http://hackage.haskell.org/trac/ghc/query?status=new&status=assigned&status=reopened&priority=high&priority=highest&milestone=6.10.2&order=priority If there is a bug not in that list that is causing you major problems, then please let us know. We expect to have a release candidate ready around the end of next week. Thanks Ian
Friends | While it is possible that we will fix some others, for the 6.10.2 | release we mainly intend to look at the high-priority bugs in the 6.10.2 | milestone. They are listed here: | | http://hackage.haskell.org/trac/ghc/query?status=new&status=assigned&status=reopened | &priority=high&priority=highest&milestone=6.10.2&order=priority | | If there is a bug not in that list that is causing you major problems, | then please let us know. Better still, if you felt able to help us by actually fixing some of the 65+ other bugs recorded against 6.10.2 that would be fantastic! Look here http://hackage.haskell.org/trac/ghc/query?status=new&status=assigned&status=reopened&milestone=6.10.2&order=priority Many are minor, many are probably quick to fix. What a great way to spend a happy afternoon, get your name in lights, and help your colleagues! Simon
This is just a quick summary of our plans for GHC 6.10.2. .. If there is a bug not in that list that is causing you major problems, then please let us know.
Hi Ian, I noticed that http://hackage.haskell.org/trac/ghc/ticket/1502 keeps getting pushed back (now 2 years old!). Perhaps the summary is misleading, because the comments make it clear that the issue is one of "normalizing" the mingw layout in GHC's copy. If the layout simply followed the standard mingw layout - just omitting parts, instead of also restructuring the parts that are copied in, that would make it easier for other tools/users. - special cases in cabal/etc could disappear - mingw could be upgraded separately - existing mingw could be used - no surprise bugs due to unusual layout (picking up wrong tools) It isn't causing me personally any problems right now, but this looks like a straightforward simplification - delaying of which causes unnecessary pressure elsewhere. It would also be nice to move to the standard layout before any Haskell Platform releases start relying on the current mess. Anything that makes Windows less of a special case ought to help, no?-) Claus Ps. It is surprising that performance bugs don't get high priority, now that distractions like extralibs are out of the ghc picture?
On Tue, Feb 10, 2009 at 07:19:53PM -0000, Claus Reinke wrote:
I noticed that http://hackage.haskell.org/trac/ghc/ticket/1502 keeps getting pushed back (now 2 years old!).
We'll do this for the new build system, as we need to rewrite the code to put gcc etc in the right place anyway. Thanks Ian
| Ps. It is surprising that performance bugs don't get high | priority, now that distractions like extralibs are out of the | ghc picture? Generally we prioritise bugs that appear to be show-stoppers, and/or are on a tier-1 platform. Having extralibs out of the way is a help, but as you'll see if you follow the link, we typically have a factor of 10 more tickets than we can deal with, at least unless more people join in, an outcome devoutly to be espoused. I believe that many are minor and could well be done by others -- but each requires reproduction, investigation, design, test case etc. I wish we could work faster, but there we are. Of course we want to focus the time we have on the tickets that are most significant to our users. If there is a particular ticket, performance or otherwise, that is particularly important to you, make sure you add a comment to explain that it's important and why; and add yourself to the cc list. http://hackage.haskell.org/trac/ghc/query?status=new&status=assigned&status=reopened&milestone=6.10.2&order=priority Simon
Ian wrote,
This is just a quick summary of our plans for GHC 6.10.2.
While it is possible that we will fix some others, for the 6.10.2 release we mainly intend to look at the high-priority bugs in the 6.10.2 milestone. They are listed here:
#2658 really needs input from the reporter (see my last comment on the ticket). Manuel
participants (4)
-
Claus Reinke -
Ian Lynagh -
Manuel M T Chakravarty -
Simon Peyton-Jones