5.1.1 release

[wiredfool]

• Build osx wheels with xcode 6.4, supporting older OSX versions. (Pillow 5.1.0's included dylibs binaries stopped working on Mac El Capitan (10.11) #3068)
• Include Fix _i2f compilation on some GCC versions #3067 ?
• Wheels for 3.7, if we can convince the pillow-wheels repo to do that easily? (Release wheels for latest stable for Python 3.7 #3074)

[wiredfool]

I'd appreciate any help on this.

[matthew-brett]

I believe it's dangerous to build 3.7 wheels before the official release, as the binary API may change.

[homm]

Include #3067 ?

I'm for it. Compilation problems are that can be fixed in minor updates

[paregorios]

Respectfully, from the user gallery: I'd prefer to see Pillow 5.1.1 not get held up for Python 3.7 official release, which is iirc still a couple months away. Because #3068. Thanks.

[wiredfool]

Ok, #3067 and xcode6.4 wheels.

[hugovk]

I've done the first steps of https://github.com/python-pillow/Pillow/blob/master/RELEASING.md#point-release on https://github.com/python-pillow/Pillow/tree/5.1.x:

---

Point Release

Released as needed for security, installation or critical bug fixes.

• Make necessary changes in master branch.
• Update CHANGES.rst.
• Cherry pick individual commits from master branch to release branch e.g. 2.9.x.
• Check Travis CI to confirm passing tests in release branch e.g. 2.9.x.
• Checkout release branch e.g.:

    git checkout -t remotes/origin/2.9.x

• In compliance with https://www.python.org/dev/peps/pep-0440/, update version identifier in src/PIL/_version.py
• Run pre-release check via make release-test.
• Create tag for release e.g.:

    $ git tag 2.9.1
    $ git push --tags

• Create source distributions e.g.:

    $ make sdist

• Create binary distributions

---

Plus release notes.

In https://github.com/python-pillow/Pillow/blob/5.1.x/docs/releasenotes/5.1.1.rst I put "... Xcode 6.4 to support at least 10.10 Yosemite" because it's not quite clear to me if 10.9 Mavericks is supported by Xcode 6.4, but we can change that if think it is.

---

Next up, resolve python-pillow/pillow-wheels#84.

[homm]

Any plans for this?

[hugovk]

If no further comments on python-pillow/pillow-wheels#84, let's merge it and go forward.

[wiredfool]

yeah. go for it.

[hugovk]

python-pillow/pillow-wheels#84 merged.

---

https://github.com/python-pillow/pillow-wheels has had three changes since last time:

• (Build on Xcode 6.4 pillow-wheels#84) Use Xcode 6.2 - needed
• (Updated libwebp to 1.0.0 pillow-wheels#85) Update multibuild - probably needed
• (Updated libwebp to 1.0.0 pillow-wheels#85) Update libwebp to 1.0.0

Is that last one a problem? libwep 1.0.0 has been updated in python-pillow/Pillow in master (#3108) after 5.1.0. Should it also go into the 5.1.x branch?

[wiredfool]

I'd rather not push a new version of webp in a point release given that it's not a current issue we're fixing and we've got 0 experience with it so far.

[hugovk]

https://github.com/python-pillow/pillow-wheels/tree/5.1.x is the 5.1.0 release commit with just Xcode 6.4 and multibuild cherry-picked.

Building now, green so far: https://travis-ci.org/python-pillow/pillow-wheels/builds/371046996

I've done these next steps:

---

• Create tag for release e.g.:

    $ git tag 2.9.1
    $ git push --tags

• Create source distributions e.g.:

    $ make sdist

• Create binary distributions

---

I don't have upload rights for the last steps, @wiredfool please could you finish off?

[yarikoptic]

this release being released would be much appreciated so Pillow is usable again on elderly OSX releases.

[hugovk]

With 5.2.0 due out in two weeks (#3154), TODO if 5.1.1 is not released:

• Delete 5.1.1 tag
• Roll back 5.1.x branch to state of 5.1.0 release

[hugovk]

Let's release these in 5.2.0 (#3154) instead.