-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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 Pillow 10.1.0 on October 15, 2023 #7348
Comments
Hello, |
Yes, #7383 will be in the October release. Everything merged to |
For the record: release is delayed from common 1st October to 15th October due to Python 3.12 support which will be released at 15th October. |
Right, and the aforementioned record on release schedule is here: https://pillow.readthedocs.io/en/stable/releasenotes/index.html#release-notes |
It's release day! About PR #7307. I merged it, but now I'm having second thoughts. Sorry for raising this last minute, but rather before the release. The release notes call it a breaking change:
https://pillow.readthedocs.io/en/latest/releasenotes/10.1.0.html#backwards-incompatible-changes We use SemVer and 10.1.0 is not a major release that would allow breaking changes. Options:
@python-pillow/pillow-team Thoughts? |
I don't think it should be a breaking change for the normal user - I find it hard to think of a safe practical use for this, and we released #3203 for It is a breaking change if you are writing your own plugins for Pillow, e.g. bigcat88/pillow_heif#122, but I don't think we consider that when creating releases. I've created #7465 to move it to a different section of the release notes, and improve the documentation about writing your own plugin. Edit: Also fdintino/pillow-avif-plugin@1853be2 |
Hmm, on the one hand, SemVer doesn't distinguish between normal users and plugins users, it's all part of the public API. But the exposure is clearly smaller, plugins do things a bit differently, and in this case it's fine to set an internal Thanks for the PR, let's go with it, and if there are other plugins we can give a heads-up to, let's do that. |
I've started the release. So far the GH wheel building is very nice and smooth! Travis CI build failed to upload the wheels to the GH release:
https://app.travis-ci.com/github/python-pillow/pillow/builds/266593993 |
I think this is because the token was originally generated against the https://github.com/python-pillow/pillow-wheels/ repo: python-pillow/pillow-wheels#156 (comment) So we need to update it for this https://github.com/python-pillow/Pillow repo and add it to https://app.travis-ci.com/github/python-pillow/pillow/settings. I'll try that. |
❯ sudo gem install travis --no-document
...
❯ travis --version
Shell completion not installed. Would you like to install it now? |y| y
1.11.1
❯ travis setup releases
Detected repository as python-pillow/Pillow/, is this correct? |yes|
resource not found ({}
)
❯ travis login
resource not found ({}
)
I need to pop out for an hour or so, to be continued... |
Not related to this release but wondering do we still need Travis to build wheels? Thinking of this as potential replacement: https://github.com/pypa/cibuildwheel |
If you're interested in a quick fix for this release, here are aarch64 wheels. As I have sometimes before, I generated them by adjusting the Travis script to upload the wheels to https://www.file.io/ aarch64-Python38-39.zip |
I would very much like to move from multibuild to cibuildwheel. Both are fantastic projects, multibuild came first, and cibuildwheel learnt a lot from multibuild (see https://github.com/pypa/cibuildwheel#credits). We're using Travis CI to build aarch64 wheels because of the available hardware. We can already build them on GHA, but it's sloooow due to emulation. See python-pillow/pillow-wheels#367. I expect cibuildwheel would be about as slow with cibuildwheel. And when we have the automation of #7390 full in place, perhaps the slowness will be acceptable. Definitely something to evaluate when the time comes. |
Thanks, I'll probably use those if |
It wasn't trivially fixable, so I used those. Thanks! Looks like we need to create a GitHub API token, then use that to login to @aclark4life The GitHub token should be scoped against this repo, and I'm not an admin here so can't do that, so can I delegate this to you? :) No rush on this, and we can create a new issue for it. |
All released, announcements to follow soon!
Thanks everyone! |
Twitter announcement: https://twitter.com/PythonPillow/status/1713600484248842255 |
Issue for this: #7485 |
Thanks to #7552, we are now using cibuildwheel. |
Highlights:
TODO
Main Release
Released quarterly on January 2nd, April 1st, July 1st and October 15th.
main
branch.main
branch.src/PIL/_version.py
CHANGES.rst
.make release-test
in a freshly cloned repo.increment and append
.dev0
to version identifier insrc/PIL/_version.py
and then:Binary Distributions
macOS and Linux
and copy into
dist/
. For example using GitHub CLI:gh run download --dir dist # select dist-x.y.z
and copy into
dist
.Windows
and copy into
dist/
. For example using GitHub CLI:gh run download --dir dist # select dist-x.y.z
Publicize Release
Documentation
Docker Images
git clone https://github.com/python-pillow/docker-images cd docker-images ./update-pillow-tag.sh [[release tag]]
The text was updated successfully, but these errors were encountered: