Closed mkitti closed 11 months ago
0.17 will drop support for Julia 1.3 and older, moving to Julia 1.6 compat.
Any plans for this release?
I'm letting the dust settle from the 0.16.15 release and the 1.14.0 HDF5_jll release. I'll probably start merging in the pull requests this week though.
@ranocha , what kind of timeline would you like to see?
The JLL overhaul was planned to happen before we continue working on the PRs linked above. As far as I know, the new JLLs should be in use now, aren't they? Is there anything else you would like to do before we can continue working on the two PRs and merge them to prepare the breaking release?
I am ready to start breaking things.
@simonbyrne @musm anything else need to be done before moving to 0.17?
Nothing from me. Lets do it.
For v0.16 branch, I think we should keep using Requires.jl only. For v0.17 should go all in on package extensions.
So you would restrict v0.17 to Julia v1.9 and newer, excluding the LTS?
I'm considering it, but let's see how difficult it is to backfill with Requires.jl. We also need to consider how to handle the filter packages such as H5Zstd.jl.
Is there an updated timeframe for v0.17? We are working on a C ↔️ Julia interaction project, and the Preferences-based custom library selection of #1061 would really help with that.
Does the current master branch work for you?
Does the current master branch work for you?
@sloede?
I would like to get some more things in with the breaking change. My target is a week after JuliaCon
Does the current master branch work for you?
I am sorry, but I have been completely swamped and not gotten around to testing it properly. A first smoke test was positive, but it is nothing that I would consider a real-world test, and I likely won't get around to it before August either :-/
Do you think we can make a new release soon?
Yea, it's on my to do list. I actually just flew into Columbus, Ohio for the HDF User Group meeting so this is the perfect place to work on this.
From our side everything works with master and v1.17 can be released.
@musm @simonbyrne anything else to do for 0.17?
I think we are about ready to release 0.17.
0.17 has been registered.
Thing to kick over to 0.18:
This is an issue to document planned breaking changes for 0.17