Firedrake meeting 2025 09 30 - firedrakeproject/firedrake GitHub Wiki

Date and time 2025-09-30 1600 UTC+1

Action Items

Pick Chair and Minuter (KS to pick)
ALL: (ongoing) triage the open issues and confirm if they are indeed still open (and perhaps provide labels)
ALL: do things with SV's branches
DH: Email to Andreas to have 2 (+ others!!!) loopy PRs merged TODO: FIND OUT WHICH PRS THESE ARE
DH: Talk to GregVernon about PR#2116.
LC: Try to merge RNH' PR: Movable VOM
PB: Profile and speed up some tests (minutes, minutes)
CW: More testing configurations (minutes)
All: Go through issues and mark with "good first issue" for new MSc/PhD contributor projects.
LC: Deprecate .at() (minutes)

Minutes

Present: CW (minuter), DH, PB, JHC, KS, LC, AG, IM, CC

Apologies:

DH/LC `.at()` deprecation

DH: Will be inconvenient for Thetis folk. VoM not currently fast enough for particle tracking (which is also the issue with streamplot).
DH: Thetis will have to use ._at() until this is fixed.

CW: Should we release 2025.4.3?

Hear me out. When we make new releases of UFL, pyadjoint, FIAT etc then 2025.4.2 will break because we do not constrain their versions (eg). Users know that we will stop maintaining 2025.4.x when we release 2025.10.0, but this will soften the transition.

DH: Yep. Do this.
JHC: PETSc have released, green light.
DH: And for the next release do the merge in a PR and check that main branches of downstream packages pass.
CW: I want to make the release from a branch that is not actually release. That means that we can test upstream release branches in our own release CI.
DH: And tell people in announcement that we won't patch 2025.4.x any more.