
Hi all, GHC 8.10.6 was released last week, with high hopes of finally putting an end to the long running saga of the GHC 8.10 series. Unfortunately, this was not to be the case as we soon discovered #19950, an issue that we claimed to have fixed in the 8.10.6 release, was still affecting the released compiler. #19950 is caused by a bug in newer Apple toolchains (specifically XCode 12) where programs compiled with affected versions of XCode are not backwards compatible with configurations running older version of XCode (certain versions of XCode 11). It surfaced in GHC 8.10.5 since we upgraded the toolchain on our Darwin builders to one of the affected versions. The original fix/workaround for #19950 was tested on the master and GHC-9.2 branches and found to be working, and so backported to the 8.10 branch. Unfortunately, Darwin releases for 8.10 are still done using the Make build system, which did not pick up the extra linker options needed to work around the issue. It places a heavy burden on developers to have so many active branches of the compiler to keep in mind, and the current situation with 4 active branches is simply not sustainable. As the oldest currently active branch, it is currently a priority to retire the 8.10 branch of GHC from active development as soon as possible. We have now fixed and verified the fix for #19950 on the 8.10 branch and prepared a GHC 8.10.7 release including it. As of now, the only change in GHC 8.10.7 is to link the x86_64 darwin release build with a few extra linker options to work around #19950. If you have any other critical issues that prevent you from using GHC 8.10(.6), please raise them soon by either pointing to existing tickets on the tracker or creating a new one. We are planning to cut the new release as soon as early next week, and we are really hoping that this would be the final release in the 8.10 series. Cheers, Zubin.

Hi Zubin, Thank you for message! On Sat, Aug 21, 2021 at 6:58 PM Zubin Duggal wrote:
As the oldest currently active branch, it is currently a priority to retire the 8.10 branch of GHC from active development as soon as possible.
With talk of retiring the 8.10 branch, I think it might be worthwhile to remind folks that GHC 8.10(.6) is still the most recent release that is suitable for production use. GHC 9.0.1 is *not* suitable for production use due to major issues, and GHC 9.0.2 is not ready yet. Major GHC 9.0.1 issues: * https://mail.haskell.org/pipermail/haskell-cafe/2021-March/133540.html * https://gitlab.haskell.org/ghc/ghc/-/issues/19345 * https://gitlab.haskell.org/ghc/ghc/-/issues/19976 GHC 9.0.2 progress: * https://gitlab.haskell.org/ghc/ghc/-/milestones/367 Thank you to the GHC developers for great progress. Four active branches does indeed sound daunting. I hope that the GHC 8.10.7 release goes well, and I am really looking forward to a production-ready release of GHC 9 whenever it is ready! Cheers, Travis

Am So., 22. Aug. 2021 um 09:33 Uhr schrieb Travis Cardwell via Haskell-Cafe
With talk of retiring the 8.10 branch, I think it might be worthwhile to remind folks that GHC 8.10(.6) is still the most recent release that is suitable for production use. GHC 9.0.1 is *not* suitable for production use due to major issues, and GHC 9.0.2 is not ready yet. [...]
Exactly, The 8.10 series is the *only* one with full tool support at the moment, so retiring this seems to be a bit premature. The only recent LTS versions on Stackage are for 8.10, 9.0 is only available via nightly, and there is no 9.2 at all. The Haskell Language doesn't have support for 9.2, either.OK, there are only alphas for 9.2 up to now, nevertheless some alphas for the corresponding tools would be nice, too. I'm totally aware of the fact that there are different people working on the different tools/compilers/libraries, but this doesn't matter at all as an "end user". The Haskell ecosystem needs much more coordination to offer a smoother user experience. Other language ecosystems are *much* more comfortable to install and use. Cheers, S.

I should clarify. By "retiring" I mean that we will not backport any more features or bug fixes to the 8.10 branch or put out new releases once 8.10.7 is out. Of course, this will only be the case if nothing critical comes up (for some definition of critical). We fully intend to ensure that GHC 8.10(.7) is a stable and robust release, ready for production use. This was the very purpose of my initial email, to ensure that there are no hidden release breaking bugs lurking somewhere. As of now, the only "critical" issue we know of in the 8.10.6 release is #19950, which will be resolved in 8.10.7. We encourage you to use GHC 8.10 as an end user or library developer, the previous email is not in any way meant to imply that we are asking you to migrate off of GHC 8.10. The purpose was simply to make sure that any (release critical) issue faced by users of GHC 8.10 is resolved in time for 8.10.7 so there is no further need of additional releases in the 8.10 series. On 21/08/22 11:00, Sven Panne wrote:
Am So., 22. Aug. 2021 um 09:33 Uhr schrieb Travis Cardwell via Haskell-Cafe
: With talk of retiring the 8.10 branch, I think it might be worthwhile to remind folks that GHC 8.10(.6) is still the most recent release that is suitable for production use. GHC 9.0.1 is *not* suitable for production use due to major issues, and GHC 9.0.2 is not ready yet. [...]
Exactly, The 8.10 series is the *only* one with full tool support at the moment, so retiring this seems to be a bit premature. The only recent LTS versions on Stackage are for 8.10, 9.0 is only available via nightly, and there is no 9.2 at all. The Haskell Language doesn't have support for 9.2, either.OK, there are only alphas for 9.2 up to now, nevertheless some alphas for the corresponding tools would be nice, too.
I'm totally aware of the fact that there are different people working on the different tools/compilers/libraries, but this doesn't matter at all as an "end user". The Haskell ecosystem needs much more coordination to offer a smoother user experience. Other language ecosystems are *much* more comfortable to install and use.
Cheers, S.
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Travis Cardwell via Haskell-Cafe
Hi Zubin,
Thank you for message!
On Sat, Aug 21, 2021 at 6:58 PM Zubin Duggal wrote:
As the oldest currently active branch, it is currently a priority to retire the 8.10 branch of GHC from active development as soon as possible.
With talk of retiring the 8.10 branch, I think it might be worthwhile to remind folks that GHC 8.10(.6) is still the most recent release that is suitable for production use. GHC 9.0.1 is *not* suitable for production use due to major issues, and GHC 9.0.2 is not ready yet.
Indeed 9.0.2 is not yet ready. However, we are actively working towards remedying this. Likewise, 9.2.1 is very close to being released. To clarify: by "retiring 8.10", Zubin means that the 8.10 series is moving into a truly "critical-bugfix-only" mode. This contrasts with our treatment of 8.10 thusfar, where we have been both trying to fix general bugs *and* backport rudimentary Darwin/ARM support. In this sense, 8.10 has been a rather odd release; in nearly all other releases the "feature-set" of a compiler release series is fixed after the N.N.1 release is cut. To stabilize Darwin support, our work has been focussed on 8.10. At this point we believe that 8.10.7 should be a very usable release and therefore we will focus our further efforts on 9.0 and 9.2. If after 8.10.7 we find an issue that renders the compiler unusable for a large numbers of users, we will of course make another release. However, we also very much hope that this won't be necessary. Cheers, - Ben
participants (4)
-
Ben Gamari
-
Sven Panne
-
Travis Cardwell
-
Zubin Duggal