Skip to content
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

Release v0.12.0 #437

Closed
jakirkham opened this issue May 26, 2023 · 13 comments · Fixed by conda-forge/numcodecs-feedstock#98
Closed

Release v0.12.0 #437

jakirkham opened this issue May 26, 2023 · 13 comments · Fixed by conda-forge/numcodecs-feedstock#98

Comments

@jakirkham
Copy link
Member

Suggesting we do another release. Could do an alpha if we wanted, but that doesn't seem necessary.

Here's the changes

Thoughts?

@jakirkham jakirkham mentioned this issue May 26, 2023
7 tasks
@martindurant
Copy link
Member

I support a release

@joshmoore
Copy link
Member

Shall we roll out 0.12.0 and 2.15.0 together, @jakirkham?

@jsolbrig
Copy link

Will 0.12.0 be released sometime soon? I'm really anticipating #428 being released.

@jakirkham
Copy link
Member Author

There was a bug encountered with NumPy 1.26+, which would be good to fix: #470

Given Python 3.12 is out, we might want to add that to CI (wouldn't expect other changes needed)

IDK if we want to wait to release for these things or release and then re-release whenever those fixes land

@joshmoore
Copy link
Member

I'd tend to get a release out ASAP (or ASAJIH -- "as soon as John is happy") and then roll another.

@jakirkham
Copy link
Member Author

jakirkham commented Oct 4, 2023

On further investigation, looks like the NumPy issue was an issue resolved in main. So a release will fix that problem (more reason to get a release out)

In terms of Python 3.12, things largely worked, but had to fix an entrypoint test issue: #471

Side note: Think it is time for us to drop Python 3.8. Have raised as issue ( zarr-developers/community#65 ). If we would rather have a release with Python 3.8 first, then drop Python 3.8 right after, that is fine. That is, as long as CI remains cooperative (there were some issues cropping up recently with Python 3.8 builds in the Python 3.12 PR). Though would also be ok just dropping it in the Python 3.12 PR (as part of this release)

@jakirkham
Copy link
Member Author

Went ahead and merged PR: #471

Going to kick off the release

@jakirkham
Copy link
Member Author

Have tagged the release here: https://github.com/zarr-developers/numcodecs/releases/tag/v0.12.0

@jakirkham
Copy link
Member Author

Seeing some sporadic issues with macOS CI where it tries to use AVX2 instructions. We might want to just turn this off completely. Doubt CI has hardware to cover this instruction. Though unsure why this issue is coming up now

Tracking in issue: #473

@jakirkham
Copy link
Member Author

Now available on PyPI & conda-forge! 🚀

Closing...

@jakirkham
Copy link
Member Author

As noted elsewhere, there were a couple bugs that surfaced recently. Most notably issue ( #478 ). Fixes for these are now in

Have cut 0.12.1. Wheels are already up. Conda-forge packages are in progress: conda-forge/numcodecs-feedstock#101

@rabernat
Copy link
Contributor

Thanks for your work @jakirkham! Appreciate it! 🙏

@jakirkham
Copy link
Member Author

Packages are up on conda-forge. Just waiting for them to mirror to CDN. Typically that takes ~15mins after upload (though could be longer)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants