<div dir="ltr"><div>I've just pushed a bunch of extra proposed extensions (then I saw that you changed the label, and then I went and found your email). It's already more than 6. In the thread, there's also a proposal for BlockArgument that has yet to be added to the proposal.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>maybe you’ll agree that<br>
if we want a predictable and reasonable frequent stream of language<br>
editions, we have to avoid such delays when feasible.</div></blockquote><div><br></div><div>I, for one, favour a regular cadence, too.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 6 Nov 2023 at 10:10, Joachim Breitner <<a href="mailto:mail@joachim-breitner.de">mail@joachim-breitner.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Committee,<br>
<br>
I’d like to get the committe involvement in GHC2024 started. The<br>
current proposal is at <br>
<a href="https://github.com/ghc-proposals/ghc-proposals/pull/613" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/613</a><br>
<a href="https://github.com/ghc-proposals/ghc-proposals/blob/joachim/ghc2024/proposals/0000-ghc2024.rst" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/blob/joachim/ghc2024/proposals/0000-ghc2024.rst</a><br>
<br>
At the moment, six changes relative to CHC2021 are proposed by<br>
committee and by community members. See the proposal for rationales.<br>
<br>
My goal is to have a decision in time for 9.10. I suggest we use<br>
November to deliberate the proposals and maybe add more changes to the<br>
list, and then vote in early December. We’ll put each change separately<br>
on the ballot.<br>
<br>
<br>
I know that there are ongoing discussions that could arguably affect<br>
how we want the next GHC20xx to look like, in particular the just<br>
opened #620, and I anticipate a desire to postpone GHC2024 until that<br>
has been decided. But I recall that we postponed GHC2023 for (among<br>
other reasons) for the same reason, and I wouldn’t be surprised that if<br>
in a year we have yet another unresolved question that seems worth<br>
waiting for. If this pattern reminds you of the GHC release process<br>
before we introduced the regular cadence, then maybe you’ll agree that<br>
if we want a predictable and reasonable frequent stream of language<br>
editions, we have to avoid such delays when feasible.<br>
<br>
<br>
So please let us know what you think of the proposed changes, what<br>
other changes you want to see, or if you have qualms about the process.<br>
<br>
<br>
Cheers,<br>
Joachim<br>
<br>
<br>
<br>
-- <br>
Joachim Breitner<br>
<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a><br>
<a href="http://www.joachim-breitner.de/" rel="noreferrer" target="_blank">http://www.joachim-breitner.de/</a><br>
<br>
_______________________________________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr">Arnaud Spiwack<br>Director, Research at <a href="https://moduscreate.com" rel="noopener noreferrer" target="_blank">https://moduscreate.com</a> and <a href="https://tweag.io" rel="noopener noreferrer" target="_blank">https://tweag.io</a>.</div></div>