> On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka <storch...@gmail.com> wrote: > > On 28.11.16 09:06, Benjamin Peterson wrote: >> I've have just updated PEP 373 to say that Python 2.7.13 release >> candidate 1 will be released on December 3. The final will follow two >> weeks later on December 17. If there are delays in the process, the >> final will likely to pushed into January. > > Could it be delayed until 3.6.0 released? I paused fixing non-critical and > non-documentation bugs while 3.6 in pre-release stage and this could include > bugs that affect 2.7. > > In additional, we always receive increased number of bug reports in the first > one or two weeks after releasing new Python version. Some of these reports > are about regressions introduced by bugfixes. If delay bugfix releases after > new version release, we could fix regressions caused by backported bugfixes > and make bugfix releases more reliable.
+1 on delaying 2.7.13 for a bit. As long as it doesn't muck up Benjamin's schedule, the extra time would be helpful (Python 3.6.0 got all the focus recently). Raymond _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com