Release Pillow 4.0.0 on Jan 1, 2017

[wiredfool]

• Release notes for dropping 2.6/3.2 Drop support for Python 2.6 #2192
• Release notes for dropping olefile in favor of a vendored version Remove vendored version of olefile Python package in favor of upstream #2199
• Release notes for handles_eof Removed the handles_eof flag in the decoder, as there are no users of it #2223
• Release notes for stretch Remove depreciated internal "stretch" method #2276
• Have bikeshed discussion about version number.

[hugovk]

That bikeshed won't paint itself. So:

We don't really have a formal policy, other than a tradition to use a major.minor.micro versioning. We update the micro version for https://github.com/python-pillow/Pillow/blob/master/RELEASING.md#point-release for security, installation or critical bug fixes, but we're not covering the micro number here.

We're not following semantic versioning, as we release quarterly with whatever has been merged, which inevitably contains both functionality added in a backwards-compatible manner (semver minor bump) and backwards-compatible bug fixes (semver micro bump). We generally try to avoid incompatible API changes (semver major bump), but they sometimes come along too.

I'm not too bothered about 3.5.0 or 4.0.0, but here's some pros and cons.

Reasons for 3.5.0:

• Last release was 3.4.0.
• In Release Pillow 3.0 after 2.9? #1087 we decided 3.0 would follow 2.9 instead of 2.10.

Reasons for 4.0.0:

• Makes it clearer something big has changed: Pillow's no longer backwards compatible with Python 2.6 and 3.2.
• It follows suit with Pillow 2.0.0 in dropping Python versions 2.4 and 2.5, and also be much easier to remember.
• In Release Pillow 3.0 after 2.9? #1087 we decided 3.0 would follow 2.9 instead of 2.10, i.e. bumping major version when minor reached 9, but we didn't talk about or rule out other big reasons for bumping major versions.
• From Release Pillow 3.0 after 2.9? #1087: "Is the release after 2.9 big or important enough to be given a 3.0 version number? Well, 10 releases of Pillow is a great achievement in itself, especially with quarterly releases."
  • This suggests other "big" things merit a major version bump.
• From Release Pillow 3.0 after 2.9? #1087: "Having said that, if anything "big" comes along before 2.9, it might make sense to bump up to 3.0. For example Python 3 support warranted the bump to Pillow 2.0."
  • Dropping support for two Python versions (2.6/3.2) may be big enough.

More welcome for either version.

[aclark4life]

I am pro "make the version number noticeably different so folks notice the change". There are likely some projects in which I'd prefer sequential "don't draw attention" versioning, but Pillow is probably not one of them.

[aclark4life]

Is this the "release 3.5 (or 4) on Jan 1 2017" issue? If so, can we standardize the title? E.g. "Release Pillow VERSION on DATE"?

[aclark4life]

🏏 s… Do we have any consensus on 3.5 vs. 4? Note that while I've stated my opinions, I'm not doing all the work so I can easily be overridden. But please let me know because I want to update the milestones, etc.

[wiredfool]

I was leaning to 4.0. I think that's the general consensus, and there are no objections that I've heard.

[gpraceman]

Will this add support for Python 3.6?

[aclark4life]

@gpraceman I believe so, yes. When in doubt, check the master branch.

[wiredfool]

I'm ready to increment the version and tag 4.0. @cgohlke Do you need the source uploaded to Pypi to build? I'm thinking that we might avoid some questions if we tag and build, then upload binaries at the same time as source.

[wiredfool]

@cgohlke Works for me. Thanks for building for us.

[wiredfool]

Tagged, OSX and Linux wheels built, but without the PR for libpng. (which is odd, unless it's a dependency of one of the dependencies, because it's not required for the library)

[keikoro]

Having never uploaded anything to PyPI myself before, I'm not really familiar with the jargon (also, it looks like some messages were deleted from this thread?) and now I'm a little confused about the version change vs. the new version of Pillow not (yet) being available on PyPI. Maybe one of you could help?