Previous meeting wrap-up Current affairs Release of Cabal 3.16Ben sent out a call for boot library maintainers w.r.t. the planned GHC 9.14 release: alpha in June and final release in September. Cabal is expected to release 3.16.0.0 version of the library. Do we want to release the library earlier and the tool a bit later (prefereably before the final GHC release)? Artem: I think it'd be good to try to release the library before the alpha release of GHC (June) and the tool before the final GHC release (September). stack is doing prereleases with ghcup support. Should we try it for 3.16? Introduce a cabal proposal process? Matthew has proposed the investigation of the idea of a having a proposals process for cabal.

Previous meeting notes. Previous meeting wrap-up Current affairs [Mikolaj] if Hecate is around, let's do a postmortem of 3.12.1.0 and discuss the scope (e.g., backporting policy) of 3.14 (but if not, let's postpone to next chat), see https://github.com/haskell/cabal/issues/10193#issuecomment-2304589970 and also https://github.com/haskell/cabal/issues/10241 Review needed #10259 API checkingprobably on hold for next several weeks awaiting reviews by Matthew and HécateArtem thinks it's less invasive than the code formatter and also perhaps easier to revert or stop requiring the checks to pass if it's too costly on contributors (as opposed to on maintainers)