Release Pillow 7.0.0 on January 2, 2020

[radarhere]

Release checklist:

• Open a release ticket e.g. Release Pillow 5.2.0 on July 1, 2018 #3154
• 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.2.x
  git tag 5.2.0
  git push --all
  git push --tags

• Create source distributions e.g.:

  make sdist

• Create 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
  ./update-pillow-tag.sh [[release tag]]

• Download distributions from the Pillow Wheel Builder container.

  wget -m -A 'Pillow-<VERSION>*' \
  http://a365fff413fe338398b6-1c8a9b3114517dc5fe17b7c3f8c63a43.r19.cf2.rackcdn.com

---

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

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 up-to-date with the release changes

[radarhere]

Any volunteers to manage this release?

[hugovk]

I'm in the middle of moving, so unfortunately might not have enough time for this one, so it'd be great if someone else could do it.

---

I'd also like to suggest that no-one should feel an obligation to work on a public holiday wherever they may be (as 1st January is in many countries), so would support adjusting the release policy to reflect this. Of course, if 1st January suits the release manager, then that's fine.

PyPI stats show weekend downloads are half those on weekdays, suggesting fewer people working, so I bet fewer people will need a new release on 1st January.

---

Similarly, I'll open a new issue for this at some point, but briefly: CPython is moving from an 18-month to an annual release cycle, with releases in October (PEP 602). CPython 3.9 is currently scheduled for 2020-10-05 (PEP 596).

To prevent double work us making a 2020-10-01 release (eg. 7.2.0), and then a patch version (eg. 7.2.1) a few days later with Windows wheels, I'd like to suggest we make the October release when the new CPython 3.9 is ready for us to support it.

[Mapiarz]

Hi! Will version 7.0.0 support Python 2.7?

[hugovk]

Hi! No, Pillow 7.0.0 supports Python 3.5 and up. Pillow 6 is the last to support Python 2.7.

See #3642.

[aclark4life]

@hugovk Fine to adjust schedule to avoid holidays and @radarhere thanks for taking this one!