03/08/2023 Cabal meeting minutes

[Artem Pelenitsyn]

Thanks a lot Hécate!

Re: adding Nix-related stuff. I was thinking about it a lot and was
planning to work on it after I'm free (in the Fall). If Yvan has a plan,
that's amazing! We accumulated a lot of stuff that we use in CI (Sphynx,
Fourmolu, HLint, doctest… maybe Weeder in the future?), so I think it's
exactly the right time to get this kind of solution. Full disclaimer, I use
NixOS and get to feel the mild annoyance of not having the support.

In the past we heard concerns about maintenance cost of a Nix-based
solution. I just wanna say, I'm ready to put some of my time to make sure
it's up and running. I'd just make one request: please-please add a CI job
that would check that this solution is up to date. It doesn't have to run
tests, I think. Just lint and build would be enough I think.

--
Best, Artem

On Thu, Aug 3, 2023, 2:35 PM Theophile Hécate Choutri via cabal-devel <
cabal-devel at haskell.org> wrote:

> Hi everyone
>
> You will find below the minutes of the Cabal meeting that was held on the
> 03/08/2023.
> This meeting occurs every two weeks and is absolutely open to developers,
> newcomers and stakeholders. Do contact the dev team if you want an
> invitation to the event.
>
> ---
>
> ## 3.10.2.0 patch release
>
> Hécate: The pipeline situation seems to have been fixed, as such Mikołaj &
> I are able to run GitLab pipelines for cabal. I suggest that once the
> following PRs are merged, the release process (including security fixes)
> resume. I'd ideally like it to be done by next week.
>
> * https://github.com/haskell/cabal/pull/9088
>
> ## 3.12.1.0 major release
>
> Hécate: In accordance with the planned schedule of GHC 9.8, we would like
> to perform
> a major release at the end of August. This would be a good idea to highly
> promote
> cabal-head nightlies and make sure that the 3.12.1.0 release is already
> used by people
> in all but name before we formally create the tag and publish the binaries.
>
> (f-a et al.): Things we should warn users about:
> - `cabal check`: cabal now warns about missing upper bounds. I have a PR
> ready to address
>   this (ignore some checks) but #8427 needs to be merged first.
>
> ## Other topics
>
> ### Yvan
>
> * I have a working `flake.nix` and `shell.nix` that declare my dev
> environment to work on Cabal, do you think I should share it in a PR?
> * I was about to write a detailed issue where I explain why
> https://cabal.readthedocs.io/en/latest/nix-integration.html doesn't work
> at all (or it's very poorly documented and I don't understand how to
> properly use it). Instead of fixing it, I'm in favor of removing it because
> I think it's overall not a good idea to have this kind of integration.
>   * Hécate: Action Item: We should take the pulse of the community for a
> couple of releases. We should point to https://nixos.wiki/wiki/Haskell
> for transition.
> * If time permits, I also wanted to have feedback on my currently open PRs
> https://github.com/haskell/cabal/pulls/yvan-sraka.
>
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/cabal-devel/attachments/20230803/0929dc9e/attachment.html>