Patches I would like merged: * Short ByteString Patch - seems stalled again * My patches to allow compacting a ModIface - Need to put these up for review * Make Q (TExp a) a newtype (Proposal 195 -https://github.com/ghc-proposals/ghc-proposals/pull/195) - Not yet written but will not be a big effort Cheers, Matt On Thu, May 21, 2020 at 8:48 PM Ben Gamari wrote:

Domínguez, Facundo writes:

...

Hello Ben,

Matthías Páll and I are working on an implementation of QualifiedDo [1] with the aim to get it merged on time. We are trying to get a small pull request submitted in the first week of June.

Thanks for the heads-up, Facundo! I've added this to the milestone.

Cheers,

- Ben _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

In that case I should perhaps try to get in !1102, which makes all the fixed-sized prim types always available, in too? I'm fine either way, but figure it's nice for any CPP to deal with the fixed and bignum numeric representation changing across a single release, and the schedule gives us time to patch important packages that need it between mid-June and the end of September. Cheers, John On 5/23/20 6:49 AM, Sylvain Henry wrote:

Hi Ben,

ghc-bignum (!2231) is ready to be merged for 8.12. We are just waiting for bytestring/text maintainers to merge 2 simple patches.

Thanks, Sylvain

On 05/05/2020 20:12, Ben Gamari wrote:

...

Hi everyone,

The time is again upon us to start thinking about release planning for the next major release: GHC 8.12. In keeping with our 6-month release schedule, I propose the following schedule:

* Mid-June 2020: Aim to have all major features in the tree * Late-June 2020: Cut the ghc-8.12 branch * June - August 2020: 3 alpha releases * 1 September 2020: beta release * 25 September 2020: Final 8.12.1 release

So, if you have any major features which you would like to merge for 8.12, now is the time to start planning how to wrap them up in the next month or so. As always, do let me know if you think this may be problematic and we can discuss options.

Cheers,

- Ben

_______________________________________________ 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