-
Notifications
You must be signed in to change notification settings - Fork 49
get ready for 3.0.0 #530
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
get ready for 3.0.0 #530
Conversation
Shall we push 3.0 out? Any final thoughts? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, feel free to ship it whenever you're ready!
@@ -1,10 +1,10 @@ | |||
## Version 3.0.0 (release date TBD) | |||
## Version 3.0.0 (released 26 April 2025) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Release date needs to be corrected.
[func@version] | ||
[class@Image] | ||
[func@Image.bandjoin] | ||
[meth@Image.add] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[meth@Image.add] | |
[method@Image.add] |
ok, 3.0 is released! |
I updated the docs (using 8.17) to get ready for 3.0.0.
Any thoughts? One thing I noticed is that if course the new [method@Image.thing] links are in the pyvips docs now (obviously), which I hadn't thought of.
Perhaps we should translate these to RST style in the doc generator?