🦔 v3.12.x

[bjlittle]

Manager	Buddy	Milestone	Feature Branch	Project
@pp-mo	@ESadek-MO	v3.12	v3.12.x	🦔 v3.12.0

Minor Release	Status	Date	RTD	Release	conda-forge	PyPI
v3.12.0rc0		10-03-2025	RTD	Release	conda-forge	PyPi
v3.12.0		24-03-2025	RTD	Release	conda-forge	PyPI
v3.12.1		30-04-2025	RTD	Release	conda-forge	PyPI

[trexfeathers]

From discussion with @bjlittle and @pp-mo: we are wondering if we can focus this release on solving:

• Common agreement on loading CF non-compliant NetCDF files #5165

[pp-mo]

@schlunma @bouweandela @valeriupredoi just a heads-up ....
We have had some problems with progress in 3.12 sprint work and are considering re-planning this release

• delaying release dates by ~1 week.
• not including a solution to Bounds of derived variable are not read correctly #3678 which had been planned (Bounds on derived coords #6190) -- since we have hit problems, and it is still unresolved

Otherwise, please

• refer to 3.12 sprint board for what is planned
• expect new dates of approx ...
  • RC = 2025-03-10
  • 3.12.0 = 2025-03-24
  • (TBC shortly)
• Please respond if this is causing concern

[valeriupredoi]

many thanks @pp-mo 🍺 No concern at my end of (very DevOps-y technical) work, let me know if I can help in any way

[bouweandela]

I would prefer the delay and including a fix for #3678.

Any chance that a fix for #6188 can still be included? This is a pretty severe bug that affects cube and coordinate equality checks. I had a go at fixing it in #6325, but if you prefer to fix it in a different way that would also be great.

[pp-mo]

I would prefer ... including a fix for #3678.

hmmm... well so would we, and it was prioritised, but at present it is just looking like a bit of a blocker.
I'll keep you posted, I think that's the best we can promise right now.

Any chance that a fix for #6188 can still be included?

Well, I am looking into it again, but I need a bit of time ... so far trying to work out performance implications, whether they are serious and/or inevitable.

[bouweandela]

I looked at those a bit too and fixed the benchmarks in #6339 to get a more realistic report. I noticed a small inefficiency when looking at the profiling results that I think can be solved easily to compensate at least in part for the performance loss in the specific case used for the benchmark, so implemented that change in #6337.

[pp-mo]

Update 2025-03-06

We are still planning to cut a 3.12 release on Monday, i.e. 2025-03-10.

Remaining tasks:

• Make array equal work with masked Dask arrays and add tests #6325 After some considerable more effort from @bouweandela , this is now merged
• Bounds of derived variable are not read correctly #3678 unfortunately is still very much stuck without an acceptable solution. Though we do have a clear plan, it will just take more work
• Tolerant handling of standard_name and dimension coordinate loading #6338 ..
• .. and Combine cubes 2 #6334 :
  • I hope to have these also completed by Monday, but they are also still not certain

[pp-mo]

Good new, the RC is now out !
Available on PyPI and conda-forge as per usual.
https://github.com/SciTools/iris/releases/tag/v3.12.0rc0

[pp-mo]

Now complete !
https://github.com/SciTools/iris/releases/tag/v3.12.0

[trexfeathers]

We have now released Iris v3.12.1.

This contains a single change, to make us compatible with Setuptools versions 80 and higher (a breaking incompatibility was discovered earlier this week #6424). This fix is needed for anyone that uses pip install -e with Iris, or any setup.py commands.

Ping @thebaptiste

[thebaptiste]

Many thanks !