Hi Sebastian, I don't think I understand the severity of #21229, is it an incorrect runtime result? If so, we should definitely fix it before 9.4.1. Thanks for bringing it to my attention.
Matt On Wed, Apr 6, 2022 at 1:18 PM Sebastian Graf <sgraf1...@gmail.com> wrote: > > Hi Matthew, > > Depending on whether https://gitlab.haskell.org/ghc/ghc/-/issues/21229 is > deemed a blocker for 9.4 (I'd say it is, but YMMV), we should include > https://gitlab.haskell.org/ghc/ghc/-/merge_requests/7788 in the list. > Perhaps we should make it dependent on whether !7788 is ready to merge by May > or whether it ends up as the only patch that holds back the release. > > Sebastian > > Am Mi., 6. Apr. 2022 um 11:00 Uhr schrieb Matthew Pickering > <matthewtpicker...@gmail.com>: >> >> Hi all, >> >> We have now forked the 9.4 branch. >> >> There are a few outstanding patches which have not yet been finished >> but which are essential to the release. >> >> * (#21019) Windows Toolchain Updates - Ben >> * (#20405) Partial Register Stall - Ben/Andreas >> * (!7812) Syntactic Unification - Sam >> >> The target date for the first alpha for 9.4.1 is 1st May. >> >> We have started preparing the 9.2.3 release in order to fix issues >> discovered in the 9.2.2 release. I will post separately to the list >> shortly when the schedule for this release is confirmed. The release >> manager for this release is Zubin. >> >> Cheers, >> >> Matt >> _______________________________________________ >> ghc-devs mailing list >> ghc-devs@haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
