GHC 7.8 Release Status & Schedule

Friends, After talking with Simon yesterday, we have some idea of how the release will go. As I'm sure you're aware, the release is winding down rather quickly, and it will be a fantastic one hopefully :) Now that all the features have landed, we're going into bugfixing mode. The schedule is, roughly: - Nov 1st: Cut branch, and I plan on making a 7.8 RC1 available the same day, for several platforms. - Release will be ~3 weeks out from there, approximately Nov 25th. This gives us a month of solid bugfixing. During the 3 weeks with the 7.8 branch open, I'm a bit hesitant to land massive changes, so that our branches don't diverge too far. OTOH, a few things can probably land in this timeframe with minimal disturbances (such as the Applicative-Monad change.) If you want to land something in that time frame, please just ask me. On the whole, things actually feel pretty good - although there a few nasty bugs to sort out, the uptake in community involvement has simply been fantastic (definitely related to the number bugs we've found,) and I think we're on track to sort the remaining stuff out. A great thanks to all of the new people helping out! And if you want to help even more, please check out the tickets remaining for 7.8.1: http://ghc.haskell.org/trac/ghc/query?status=!closed&milestone=7.8.1&order=priority If you think you can take on a bug, please assign it to yourself so we know what's going on. Note: if the bug isn't *high* or *highest*, it's unlikely to get looked at, at least by me! It won't be rejected if you submit a patch, but I'm simply not going to be able to get to it I'm afraid. So please grab something, and go for it! I am also reminded that the GHC October Status report will be due shortly - I'll take some time to write it up, and follow through here on the list (and glasgow-haskell-users) so interested parties can read up on what is happening. -- Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/

On Sat, Oct 5, 2013 at 9:25 AM, Austin Seipp
- Nov 1st: Cut branch, and I plan on making a 7.8 RC1 available the same day, for several platforms.
Hi, Austin - Thanks for writing this up. One of the factors that's blocking my ability to build Hackage packages is that Hackage does not contain versions of a number of bundled-with-GHC packages that have versions matching the versions shipping with HEAD. It would unblock that process somewhat if you were to upload new versions of unix and various other packages that are not yet in sync fairly soon, preferably well before cutting the branch. Thanks!

On Wed, Oct 9, 2013 at 4:07 PM, Bryan O'Sullivan
One of the factors that's blocking my ability to build Hackage packages is that Hackage does not contain versions of a number of bundled-with-GHC packages that have versions matching the versions shipping with HEAD. It would unblock that process somewhat if you were to upload new versions of unix and various other packages that are not yet in sync fairly soon, preferably well before cutting the branch. Thanks!
+1. Forgetting to upload GHC released packages altogether (even after the release) has been a problem in the past. I think we should aim for making releases of all the packages GHC ships with before we make the actual release. It will make sure 1) that's not forgotten and 2) people have more time to fix their packages. There's clearly a tension here: GHC might change last minute and break one of the just released packages again, forcing another release. If we release the packages once we enter feature freeze for GHC, that should be a rare occurrence.

Indeed. There's a few straggling things but overall we're in feature freeze overall right now, right? On Wednesday, October 9, 2013, Johan Tibell wrote:
On Wed, Oct 9, 2013 at 4:07 PM, Bryan O'Sullivan
javascript:;> wrote: One of the factors that's blocking my ability to build Hackage packages is that Hackage does not contain versions of a number of bundled-with-GHC packages that have versions matching the versions shipping with HEAD. It would unblock that process somewhat if you were to upload new versions of unix and various other packages that are not yet in sync fairly soon, preferably well before cutting the branch. Thanks!
+1. Forgetting to upload GHC released packages altogether (even after the release) has been a problem in the past. I think we should aim for making releases of all the packages GHC ships with before we make the actual release. It will make sure 1) that's not forgotten and 2) people have more time to fix their packages.
There's clearly a tension here: GHC might change last minute and break one of the just released packages again, forcing another release. If we release the packages once we enter feature freeze for GHC, that should be a rare occurrence. _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org javascript:; http://www.haskell.org/mailman/listinfo/ghc-devs
participants (4)
-
Austin Seipp
-
Bryan O'Sullivan
-
Carter Schonwald
-
Johan Tibell