[python-committers] IMPORTANT: Python 3.6.2 Maintenance Release Release Candidate in 3+ days (Monday 2017-06-12 12:00 UTC)

[Ned Deily]

We are approaching the end of the second calendar quarter of 2017 and, according to PEP 494, it's time to start producing the second maintenance release for the 3.6 series.  The schedule calls for the release candidate to be produced on Monday 2017-06-12 UTC.  As was the case with previous 3.6.x releases, the plan is for the release candidate to be the same as the final release, that is, no additional changes go in after the release candidate except for any showstopper critical problems that might be discovered with rc1.  So please plan to get any security fixes, bug fixes, and documentation changes you think should be in 3.6.2 merged in ASAP.  The 3.6.2 final is planned for two weeks following rc1, that is, on 2017-06-26.  The next 3.6 maintenance release (3.6.3) is planned to follow about 3 months later, so most likely in 2017-09.

A reminder that the 3.6 branch will remain open for checkins throughout the 3.6.2rc and final cycle.  Once 3.6.2rc1 is tagged, new commits to the 3.6 branch will release with 3.6.3.  As always, if you find any problem in 3.6.2rc1 that you may believe should be corrected in 3.6.2, please ensure the problem is documented in a new or existing open issue on bugs.python.org, ensure that the Priority field of the issue is set to "release blocker", and that "Python 3.6" is included in the selected Versions.  Comments or tags on github Pull Requests are NOT sufficient!

Thanks again for all of your efforts in bringing 3.6 into the world and for helping now to make it even better!

https://www.python.org/dev/peps/pep-0494/
http://cpython-devguide.readthedocs.io

--
  Ned Deily
  nad at python.org -- []