[ghc-steering-committee] GHC20xx review; GHC2022 yes or no?

Mon Oct 11 13:59:13 UTC 2021

 Skipping seems like the most sensible option.

Regards,
Alejandro

El 6 oct 2021 14:17:58, Spiwack, Arnaud <arnaud.spiwack at tweag.io> escribió:

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