<div dir="ltr">I agree with skipping.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 6, 2021 at 10:33 AM Simon Peyton Jones via ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</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">> Anyways even more the reason to skip GHC2022<br>
<br>
I'm fine with doing that.<br>
<br>
Simon<br>
<br>
PS: I am leaving Microsoft at the end of November 2021, at which point <a href="mailto:simonpj@microsoft.com" target="_blank">simonpj@microsoft.com</a> will cease to work. Use <a href="mailto:simon.peytonjones@gmail.com" target="_blank">simon.peytonjones@gmail.com</a> instead. (For now, it just forwards to <a href="mailto:simonpj@microsoft.com" target="_blank">simonpj@microsoft.com</a>.)<br>
<br>
| -----Original Message-----<br>
| From: ghc-steering-committee <ghc-steering-committee-<br>
| <a href="mailto:bounces@haskell.org" target="_blank">bounces@haskell.org</a>> On Behalf Of Joachim Breitner<br>
| Sent: 06 October 2021 09:29<br>
| To: Richard Eisenberg <<a href="mailto:lists@richarde.dev" target="_blank">lists@richarde.dev</a>><br>
| Cc: <a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
| Subject: Re: [ghc-steering-committee] GHC20xx review; GHC2022 yes or<br>
| no?<br>
| <br>
| Right, I thought it wasn't, and phrased the mail accordingly. But then<br>
| I noticed that the timeline in<br>
| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitl" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitl</a><br>
| <a href="http://ab.haskell.org" rel="noreferrer" target="_blank">ab.haskell.org</a>%2Fghc%2Fghc%2F-<br>
| %2Fmilestones%2F365&data=04%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cb7fbe<br>
| c91949c4c109ed608d988a37091%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0<br>
| %7C637691058751508157%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ<br>
| IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=TBDthig0E0<br>
| aXoyYtUYaTaXLHi%2FWQAenQjAlWh5upptU%3D&reserved=0 said 2021, not<br>
| 2022, and that it already is in nixpkgs, so I drew the wrong<br>
| conclusions, and changed my mail again<br>
| <br>
| Anyways even more the reason to skip GHC2022<br>
| <br>
| <br>
| 05.10.2021 23:50:06 Richard Eisenberg <<a href="mailto:lists@richarde.dev" target="_blank">lists@richarde.dev</a>>:<br>
| <br>
| > What makes you say 9.2 has been released? I don't think it has been.<br>
| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww</a>.<br>
| <a href="http://haskell.org" rel="noreferrer" target="_blank">haskell.org</a>%2Fghc%2Fdownload.html&data=04%7C01%7Csimonpj%40microso<br>
| <a href="http://ft.com" rel="noreferrer" target="_blank">ft.com</a>%7Cb7fbec91949c4c109ed608d988a37091%7C72f988bf86f141af91ab2d7cd0<br>
| 11db47%7C1%7C0%7C637691058751508157%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC<br>
| 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sd<br>
| ata=kWHHoWI0Zq9J8WZ2aZ5m9rIN%2FYgZWloDullgNrV2Dow%3D&reserved=0<br>
| does not list it, for example.<br>
| ><br>
| > Otherwise, I agree on holding off.<br>
| ><br>
| > Thanks for raising this!<br>
| > Richard<br>
| ><br>
| >> On Oct 5, 2021, at 3:50 PM, Joachim Breitner <mail@joachim-<br>
| <a href="http://breitner.de" rel="noreferrer" target="_blank">breitner.de</a>> wrote:<br>
| >><br>
| >> Hi Committee,<br>
| >><br>
| >> when we defined the process for GHC20xx, as written in<br>
| >><br>
| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit</a><br>
| >> <a href="http://hub.com" rel="noreferrer" target="_blank">hub.com</a>%2Fghc-proposals%2Fghc-<br>
| proposals%2Fblob%2Fmaster%2Fproposals%2<br>
| >> F0372-ghc-<br>
| extensions.rst&data=04%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7<br>
| >><br>
| Cb7fbec91949c4c109ed608d988a37091%7C72f988bf86f141af91ab2d7cd011db47%<br>
| >><br>
| 7C1%7C0%7C637691058751518154%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw<br>
| >><br>
| MDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=t<br>
| >> AlnW8KOVrcNnV3C2BZlMUfmT0BHPKX0achIeGb2L3g%3D&reserved=0<br>
| >> we wrote<br>
| >><br>
| >> Likely, the first iteration of this process will be vastly<br>
| >> different<br>
| >> from the following ones: The first one is expected to add a large<br>
| >> number of uncontroversial extensions; so the next iteration will<br>
| >> likely only make a smaller, but more controversial change.<br>
| >><br>
| >> Therefore, this proposal does not commit to a fixed cadence.<br>
| >> Instead, 6 months after the first release of a version of GHC<br>
| that<br>
| >> supports a GHC20xx set, we evaluate the outcome, the process, and<br>
| >> the perceived need of a next release. At that time we will refine<br>
| >> the processes, if needed, and set a cadence.<br>
| >><br>
| >> The first version of GHC that supported GHC20xx is 9.2, released in<br>
| March.<br>
| >> So we should do this evaluation now.<br>
| >><br>
| >> My impression is that 9.2 hasn't reached the masses yet:<br>
| >> NixOS stable doesn't even have it, and the default is at 8.10.<br>
| >> Stackage LTS is at 8.10, and nightly at 9.0 Debian is at 8.8.<br>
| >><br>
| >> So it seems premature to try to evaluate its impact, and what, if<br>
| >> anything, we should do differently for a hypothetical GHC2022.<br>
| >><br>
| >> So I suggest we postpone this review for another half year or so.<br>
| >><br>
| >> Also, I don't see why GHC2022 would be different than GHC2021. Not<br>
| >> that much has changed about GHC and its set of "should-be-default"<br>
| >> extensions since last year, has it?<br>
| >><br>
| >> So I suggest we don't work on defining GHC2022, and the next update<br>
| >> will be GHC2023 (or later).<br>
| >><br>
| >><br>
| >> What do you think,<br>
| >> Joachim<br>
| >><br>
| >><br>
| >> --<br>
| >> Joachim Breitner<br>
| >> <a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a><br>
| >><br>
| <a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww</a>.<br>
| >> joachim-<br>
| <a href="http://breitner.de" rel="noreferrer" target="_blank">breitner.de</a>%2F&data=04%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cb<br>
| >><br>
| 7fbec91949c4c109ed608d988a37091%7C72f988bf86f141af91ab2d7cd011db47%7C<br>
| >><br>
| 1%7C0%7C637691058751518154%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD<br>
| >><br>
| AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=n9P<br>
| >> oL8dXA8ZGWywvHhkUY19mrk1WBSWTYWQHX9uTm3Q%3D&reserved=0<br>
| >><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>
| >><br>
| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmai" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmai</a><br>
| >> <a href="http://l.haskell.org" rel="noreferrer" target="_blank">l.haskell.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-<br>
| committee<br>
| >><br>
| &data=04%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cb7fbec91949c4c109ed608d<br>
| >><br>
| 988a37091%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63769105875151<br>
| >><br>
| 8154%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB<br>
| >><br>
| TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2FxFajSncDl5oRbeAY%2B%2F<br>
| >> KdrSHMCuwvhruwYxNnkVgZig%3D&reserved=0<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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail</a><br>
| .<a href="http://haskell.org" rel="noreferrer" target="_blank">haskell.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-<br>
| committee&data=04%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cb7fbec91949c4c1<br>
| 09ed608d988a37091%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6376910<br>
| 58751518154%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMz<br>
| IiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2FxFajSncDl5oRbeAY%<br>
| 2B%2FKdrSHMCuwvhruwYxNnkVgZig%3D&reserved=0<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>