[GHC-Releases] GHC 9.10 release schedule and core library status

[Mikolaj Konarski]

> Mikolaj, what’s the schedule for Cabal 3.12?

I've opened a ticket for the 9.10 cabal and GHC sync point:
https://github.com/haskell/cabal/issues/9729

Whom should I assign from outside the cabal team?

BTW, is the list of new GHC 9.10 language extensions finalized?
How about GHC options? Would somebody like to see if the cabal's
list of of GHC options is up to date (I bet it's not), and which of them
require a recompilation? The same for extensions (but the list should
be up to date except for the newest extensions --- are they all listed
in 9.10 Release Notes this time?). PRs are welcome (one is already
in the merge queue, but I'm not sure if it's for GHC 9.10:
https://github.com/haskell/cabal/pull/8854).

> all major releases should be reflected as submodules in GHC source tree before GHC fork date

Am I to understand that the cabal-GHC sync should proceed
differently this time and a cabal release is expected before
the GHC release? That should be fine, but the semantics
of cabal's GHC version validation would change from
"the GHC is tested and known to work fine with cabal"
to "the GHC exists". If so, maybe we should altogether remove
the spammy "unknown GHC version" cabal warning, decoupling
cabal and GHC a bit as a welcome side-effect? Are any other
changes in cabal or GHC needed to accommodate the new process?
E.g., is the GHC extension list guaranteed to never change past
the GHC fork date?

Cheers,
Mikolaj

On Tue, Feb 20, 2024 at 10:46 AM Mikolaj Konarski
<mikolaj at well-typed.com> wrote:
>
> > Mikolaj, what’s the schedule for Cabal 3.12?
>
> The schedule is that we are looking for a release manager
> for 3.12.1 and waiting for the release of 3.10.3 in order
> not to perform two releases concurrently.
>
> > https://gitlab.haskell.org/ghc/ghc/-/wikis/GHC-status#11-major-releases says that all major releases should be reflected as submodules in GHC source tree before GHC fork date, which is AFAIU this Friday.
>
> That means cabal is going to be late. If that helps,
> 3.12.1 will be forked off the current master branch
> and, at this time, we don't plan to remove any features
> or other commits before the release.
>
> Cheers,
> Mikolaj