owned this note
owned this note
Published
Linked with GitHub
<!--
*********************************************************
*** ☞ N.B. (leave this on top!)
Every cabal-devs meeting includes:
- Previous meeting wrap-up: a summary of actions taken
with regard to points raised in the previous meeting.
- Current affairs: we need to take a look at these PRs
and help them move on.
Urgent, of various levels of importance.
- Review needed: PRs that are ready and need a final
stamp. PR authors might want to illustrate their work
to help reviewers navigate the pull request.
- Food for thought: we want to start the thinking
process amongst ourselves for things that will take
time to unfold.
May be important, but not urgent.
Meeting markdown template (see https://hackmd.io/0bfjmIdxTUyNKXwn8fBNKg)
-------------------------
# Cabal meeting (euro date here)
## Attendees
## Previous meeting wrap-up
## Current affairs
## Review needed
- [XXX PRs have the "attention: needs-review" label](https://github.com/haskell/cabal/labels/attention%3A%20needs-review)
## Food for thought
-->
# Cabal meeting (2025-12-04)
## Attendees
## Previous meeting wrap-up
## Current affairs
- meeting time: Artem will not have a conflict with the standard time, so maybe we should move the actual time (starting at half-hour) back to the standard time (starting at the hour).
## Review needed
- [XXX PRs have the "attention: needs-review" label](https://github.com/haskell/cabal/labels/attention%3A%20needs-review)
## Food for thought
# Cabal meeting (2025-11-20)
## Attendees
Artem, Brandon, Fransco A., Jappie, Kristen, Magnus
## Previous meeting wrap-up
- New cabal logo landed in the repo, thanks to fgaz for the design.
- Artem PGP key is now cross-signed with f-a’s one.
## Current affairs
- 3.16.1.0 release
- need volunteers!
- did Brandon advance with Changelog? we want them ASAP!
- note for future: we can submit GHCup post-installation notes as a part of the metadata file
- migration strategy for cabal external commands https://github.com/haskell/cabal/pull/11232
- it's merged so maybe not much point to litigate more, let's see how it goes?..
- exact-printer PRs:
- comment parser (appears to be ready for reviewing): https://github.com/haskell/cabal/pull/11252
- don't merge common stanzas (draft): https://github.com/haskell/cabal/pull/11277
- separate tests-related PR: https://github.com/haskell/cabal/pull/11285
## Review needed
- [Only 2 PRs have the "attention: needs-review" label](https://github.com/haskell/cabal/labels/attention%3A%20needs-review) \o/
## Food for thought
---
# Cabal meeting (2025-11-06) (and we start 0.5h later till December)
## Attendees
Mikołaj, Brandon, Artem, Francesco Ariis, Kristen, Francesco Gazzetta.
## Previous meeting wrap-up
* no movement on either of issues and we can just ping people...
## Current affairs
* Next 3.16 release schedule?
* maybe start the GHC-cabal coordination process right now
* only then create the main cabal release ticket with checkboxes
* Recent urgent CI fixes: anything we need to know for the future?
* (Brandon) python fix will need to be revised, since there doesn't seem to be any intention of supporting older packages in pip in the future so the constraint `!=` must become `<`
* this also means we must look at what is needed to support newer python packages, which may also mean upgrading sphinx etc.
* [Artem] external commands interface change: https://github.com/haskell/cabal/pull/11232
* [fgaz] Add revision information to plan.json https://github.com/haskell/cabal/pull/10980
## Review needed
- [3 PRs have the "attention: needs-review" label](https://github.com/haskell/cabal/labels/attention%3A%20needs-review)
## Food for thought
---
# Cabal meeting (2025-10-23) (and we start 0.5h later till December)
## Attendees
Brandon, Mikolaj, Artem, Kristen
## Previous meeting wrap-up
- v1 removal timeline / plan
- not much changed; Andreas added a couple of v1-vs-v2 tickets that he thinks are show stoppers. Bodigrim pointed out Hackage as a big v1 user.
- the other proposal, about the bytecode way support: https://github.com/haskell/cabal-proposals/pull/2
- no objections to accepting it (the Cabal changes, not the GHC changes); Mikolaj will write this in the proposal
## Current affairs
- Simon's ticket about recompilation: https://github.com/haskell/cabal/issues/11257
- it turned out we solved it some time before (https://github.com/haskell/cabal/issues/7711#issuecomment-1948000159) and Simon needs to update GHC...
- cabal exact-print strikes again; we are enthusiastic, as usual; could somebody help? even just have a look? one of the tickets: https://github.com/haskell/cabal/pull/11252
- Artem may need help from more knowledgeable folk for https://github.com/haskell/cabal/pull/11002 which has been in the draft state since June. I just need to find time to get back to it.
## Review needed
- [2 PRs have the "attention: needs-review" label](https://github.com/haskell/cabal/labels/attention%3A%20needs-review)
## Food for thought
We stick to meeting half past the usual time till December to make it easier for Artem.
---
# Cabal meeting (2025-10-09)
## Attendees
Brandon, Francesco, Mikolaj, Artem, Kristen
## Previous meeting wrap-up
- 5 last gitlab pipelines are green, so the gitlab CI pipeline backup is probably operational for the time being
## Current affairs
- People are unhappy about the form of our changelog: no way to grep through it because it's distributed over many files.
- https://discourse.haskell.org/t/what-is-the-ideal-dependency-update-workflow/13048
* it would be great to use Hecate's API check too (print-api https://github.com/Kleidukos/print-api), but its deployment in GHC (and cabal) is still future work
* in general, searching across versions would be easier in a big changelog, while searching a single release is easier now
* we are still open for proposals (and then implementations)
- Matthew: I have written a cabal proposal which aims to establish a plan for removing the v1- legacy interface. Please read, comment and offer your opinion!
- https://github.com/haskell/cabal-proposals/pull/4
- For a start, can the meeting attendees agree about the premise "We want to remove the v1- family of commands, therefore we need a plan to achieve that."? Yes, the attendees agree.
- Matthew: Could consensus be assessed on the bytecode proposal
- https://github.com/haskell/cabal-proposals/pull/2
- Let's postpone to the next meeting in order not to rush it.
- Brandon: the workaround for misformatted footnotes in the cabal documentation ([#11246](https://github.com/haskell/cabal/issues/11246)) pins us to an older version of `docutils` that may be problematic if a security update is released
- I will look into needed changes or bug reports after the cabal 3.16.1.0 release
- Shall we mention key fingerprints for maintainers? Past release managers too? Let's discuss in the ticket: https://github.com/haskell/cabal/issues/11245
## Review needed
- [3 PRs have the "attention: needs-review" label](https://github.com/haskell/cabal/labels/attention%3A%20needs-review)
- [GHC MR: Support statically linking executables properly](https://gitlab.haskell.org/ghc/ghc/-/merge_requests/14935)
- Noted. Let use know if we can help or if something very directly influencing cabal crops up.
## Food for thought
- GHC 9.14 is nearing; anything to do now re cabal 3.16.1.0? any help needed?
---
Prior notes: https://hackmd.io/X62yS0d6RxW3ybh8AmRqlw?both