-
-
Notifications
You must be signed in to change notification settings - Fork 122
announce the NumPy 2.3.0 release #865
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
✅ Deploy Preview for numpy-org ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Thank you, @charris! |
Is it something in my browser caching, I do not see the release on the front page but it is on the news page. @charris do you want me to generate and upload documentation for 2.3? |
See #866 |
It seems the directions might need more details visa-vis #866 to prevent this in the future? |
Please do. Looks like the distutils problem is getting fixed, so maybe I can do it next time. I'd also appreciate if you updated RELEASE_WALKTHROUGH so I can get it right next time. Part of keeping it updated is to make it easier for the next release manager who comes along. |
I've set up a github action to generate PDF docs for each release. I'd be happy to do the same for the html docs generation for each new release. This would stop requiring that someone builds it locally. Wdyt? Should I add it to the main repo or to numpy/docs? https://github.com/melissawm/artoo/blob/main/.github/workflows/build_numpy_pdf.yml |
I will go ahead and build the 2.3.0 docs but it makes sense to automate the docs building, even though it is a twice-a-year event. Could it use the existing requirement files? |
Yes - I'll put something together. Cheers! |
FWIW, the 2.3.0 docs are up, i also built and uploaded the pdfs. |
Thanks Matti. |
Brief description of what is fixed or changed