The security-related release blocker (bpo-29591) has been resolved; my thanks
to Victor for leading the effort.
As of now, I'm not aware of any other release blocker issues for the 3.6.2
release candidate so I'm rescheduling the code cutoff for 2017-06-16 12:00 UTC,
approximately 30 hours from now. That gives you one last opportunity to get
important fixes in for 3.6.2. As always, if you know of issues that you think
need to be resolved before the 3.6.2 release, please ensure there is an open
tracker issue for it on bugs.python.org and mark the issue as "release
blocker". To still give 2 weeks of exposure for the rc, the new target release
date for 3.6.2 final will be 2017-06-30.
--Ned
On Jun 13, 2017, at 00:09, Ned Deily wrote:
> An update on 3.6.2rc1: we have been working through a few critical and
> release blocker issues that needed to be fixed for 3.6.2. Thanks to everyone
> who has helped with them! At the moment, we have one security-related
> release blocker (http://bugs.python.org/issue29591) which I think we need to
> get addressed in 3.6.2. So, I'm delaying 3.6.2rc1 until we can get that
> resolved. That means that, for the moment, changes going into the 3.6 branch
> will likely make in into 3.6.2. I'll let you know when we are ready to tag.
>
> On Jun 8, 2017, at 23:34, Ned Deily wrote:
>> 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
[email protected] -- []
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
