<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body><div><div style="font-family: Calibri,sans-serif; font-size: 11pt;">I would much rather keep it in December, as I've already made scheduling decisions around the planned release date and there are fixes in 2.7.13 that I was expecting to be available by the end of the year. One month is highly impactful for me.<br><br>Is this schedule change going to remove the month from 2.7.14? Or are we slipping all the rest of the releases (apart from the very last one at the end of 2019, presumably)? I too would like to know the intended use of the extra time.<br><br>Top-posted from my Windows Phone</div></div><div dir="ltr"><hr><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">From: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;"><a href="mailto:benjamin@python.org">Benjamin Peterson</a></span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Sent: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;">11/29/2016 0:04</span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">To: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;"><a href="mailto:raymond.hettinger@gmail.com">Raymond Hettinger</a>; <a href="mailto:storchaka@gmail.com">Serhiy Storchaka</a></span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Cc: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;"><a href="mailto:python-dev@python.org">Python-Dev@Python. Org</a></span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Subject: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;">Re: [Python-Dev] Python 2.7.13 release dates</span><br><br></div>Okay, by popular demand, 2.7.13 now happens in January.<br><br>I'm curious what people are planning to do to 2.7 with the extra 5<br>weeks. The 2.7 branch is a place to put occasional conservative bug<br>fixes, which we aggregate and release every 6 months. It shouldn't<br>really need special attention or become less stable depending on the<br>release stage of Python 3.<br><br>On Mon, Nov 28, 2016, at 20:50, Raymond Hettinger wrote:<br>> <br>> > On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka <storchaka@gmail.com> wrote:<br>> > <br>> > On 28.11.16 09:06, Benjamin Peterson wrote:<br>> >> I've have just updated PEP 373 to say that Python 2.7.13 release<br>> >> candidate 1 will be released on December 3. The final will follow two<br>> >> weeks later on December 17. If there are delays in the process, the<br>> >> final will likely to pushed into January.<br>> > <br>> > 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.<br>> > <br>> > 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.<br>> <br>> +1 on delaying 2.7.13 for a bit. As long as it doesn't muck up<br>> Benjamin's schedule, the extra time would be helpful (Python 3.6.0 got<br>> all the focus recently).<br>> <br>> <br>> Raymond<br>> _______________________________________________<br>> Python-Dev mailing list<br>> Python-Dev@python.org<br>> https://mail.python.org/mailman/listinfo/python-dev<br>> Unsubscribe:<br>> https://mail.python.org/mailman/options/python-dev/benjamin%40python.org<br>_______________________________________________<br>Python-Dev mailing list<br>Python-Dev@python.org<br>https://mail.python.org/mailman/listinfo/python-dev<br>Unsubscribe: https://mail.python.org/mailman/options/python-dev/steve.dower%40python.org<br></body></html>