Release v2.5.0

[maxrjones]

There's been some discussions about releasing in the near future. I'm raising this issue to find more information about the timing and cut-off time for new bug-fix PRs.

[TomNicholas]

I think we should release often, and only consider failing CI (which we unfortunately have) and unrespected support claims as blockers. Therefore I think we should release as soon as we have python 3.14 support (because we claim to support this I think?). and CI passing, and anything else comes in a later release.

[maxrjones]

I think we should release often, and only consider failing CI (which we unfortunately have) and unrespected support claims as blockers. Therefore I think we should release as soon as we have python 3.14 support (because we claim to support this I think?). and CI passing, and anything else comes in a later release.

Sounds good, I'd also prefer to release more frequent releases. That said, I think it's important to figure out if #892 was accidentally breaking first (xref #919)

[TomNicholas]

Well it was deliberately breaking, in the sense that I knew about this non-listable stores restriction, but because we didn't have a test for it, I thought it was hopefully fine. But we can fix that before release.

[TomNicholas]

#922 is also potentially a blocker, as we ideally don't want to issue a release that uses pyarrow then remove that dependency one release later...

[TomNicholas]

Well it was deliberately breaking

actually it wasn't breaking at all - see #921 (comment)

[maxrjones]

Well it was deliberately breaking

actually it wasn't breaking at all - see #921 (comment)

nice!

[TomNicholas]

I want to merge #925 and #927 then release.