Release Pillow 5.3.0 on October 1, 2018

[aclark4life]

Release Checklist

Main Release

• Open a release ticket e.g. Release Pillow 5.3.0 on October 1, 2018 #3236
• Develop and prepare release in master branch.
• Check Travis CI and AppVeyor CI to confirm passing tests in master branch.
• Check that all of the wheel builds Pillow Wheel Builder pass the tests in Travis CI.
• In compliance with PEP 440, update version identifier in src/PIL/_version.py
• Update CHANGES.rst.
• Run pre-release check via make release-test in a freshly cloned repo.
• Create branch and tag for release e.g.:

    $ git branch 5.3.x
    $ git tag 5.3.0
    $ git push --all
    $ git push --tags

• Create source distributions e.g.:

    $ make sdist

• Create binary distributions
• Upload all binaries and source distributions e.g. twine upload dist/Pillow-5.3.0-*
• Create a new release on GitHub
• In compliance with PEP 440, append .dev0 to version identifier in src/PIL/_version.py

Binary Distributions

Windows

• Contact @cgohlke for Windows binaries via release ticket e.g. Release 2.9.0 on July 1, 2015 #1174.
• Download and extract tarball from @cgohlke and twine upload *.

Mac and Linux

• Use the Pillow Wheel Builder:

    $ git clone https://github.com/python-pillow/pillow-wheels
    $ cd pillow-wheels
    $ git submodule init
    $ git submodule update
    $ cd Pillow
    $ git fetch --all
    $ git checkout [[release tag]]
    $ cd ..
    $ git commit -m "Pillow -> 5.3.0" Pillow
    $ git push

• Download distributions from the Pillow Wheel Builder container.

Publicize Release

• Announce release availability via Twitter e.g. https://twitter.com/PythonPillow/status/1013789184354603010

Documentation

• Make sure the default version for Read the Docs is the latest release version, i.e. 5.3.0 rather than latest e.g. https://pillow.readthedocs.io/en/5.3.x/

[radarhere]

Is there anything that anyone would particularly like to see in this release?

[aclark4life]

@radarhere Good q. I like to try to make sure all issues are triaged and include everything that we can possibly include based on the backlog of requests. If we tag every untagged issue, that should give us a good idea of what is realistic to include by Oct 1. Not to mention, asking for updates on various outstanding issues and either getting a reply or not.

[ghost]

• Well, Fix builds with --parallel #3272 would simplify distro's jobs and make pillow move away from it's mp_compile hack.

[hugovk]

• Would be nice to get the much-wanted Add line width parameter to rectangle and ellipse-based shapes #3094 in.

Release notes

What else important needs adding to 5.3.0.rst?

• Add feature: ImageOps.colorize to support three colors #3242
• Added line joints #3250
• Read/Save RGB webp as RGB (instead of RGBX) #3298
• Added ImageOps pad method #3364
• Adding support to reading tiled and YcbCr jpeg tiffs through libtiff #3227?

Here's a big list of commits since 5.2.0.

[radarhere]

Okay, working my way through the checklist - @cgohlke would you be able to provide Windows binaries? Thanks!

[cgohlke]

Here you go.

[radarhere]

Thanks very much @cgohlke

Okay, uploaded and released, although I don't have access to the Pillow Twitter account or Read The Docs account for the last two items in the checklist.

Thanks to everyone involved in this release.

[wiredfool]

I've updated RTD, we should get you on there @radarhere

Thanks for running the release this time.

[hugovk]

Thanks! I've added radarhere as a maintainer to RTD.

https://readthedocs.org/dashboard/pillow/users/

[wiredfool]

I was just going to say, it looks like he has access.

But race conditions.

[hugovk]

https://twitter.com/PythonPillow/status/1046694777150984192

[aclark4life]

@hugovk Can you share pw for Twitter with @radarhere ?

Thanks @radarhere, @python-pillow/pillow-team, all! Great job @radarhere; I'd say let's toggle back and forth now between @hugovk and @radarhere for future releases, unless folks have other suggestions.

[hugovk]

Shared!

Fine by me, except it's possible I might be away on 2018-01-01 meaning it might have to wait a couple of days.

[aclark4life]

@hugovk OK well we'll figure it out, I can always do it 2018-01-01 if no one else is available.