-
Notifications
You must be signed in to change notification settings - Fork 543
Prepare to release 3.11.0 #2405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2405 +/- ##
=======================================
Coverage 89.58% 89.58%
=======================================
Files 17 17
Lines 2391 2391
=======================================
Hits 2142 2142
Misses 249 249 ☔ View full report in Codecov by Sentry. |
When is the release date? Would it be possible to add support for libhdf5-1.14.4, due out later next week? |
There isn't a set date, but Numpy 2.0 is coming quite soon, and I imagine there are downstream packages that would like to test with Numpy 2.0rc1 and h5py before Numpy 2 is final. So there is some time pressure. Do you know how much effort supporting HDF5 1.14.4 is likely to be? Is #2403 likely to be the only issue? |
There's native (libhdf5) support for float16 datatype. I have branch and will make a PR so the changes can be discussed. |
Please do! My instinct, though, is that cutting over from our added float16 type might be thorny enough that we want to get 3.11 out the door before tackling that. Let's see what the PR looks like, though. |
See #2406. |
3.11 is out on PyPI now. Unfortunately we don't have Linux aarch64 wheels at the moment. These were built on Travis CI using their 'partner queues', where ARM & IBM provide their respective CPU architectures for open source projects to use. Travis builds haven't been launching for a few months; I asked Travis support about this a few days ago, but so far there's no movement. Maybe this will come back for a future release, maybe we'll move it to another CI provider, or maybe it's just more than we have room to support. 🤷 |
rever steps
version_bump
andchangelog
, followed by manual cleanup.