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.
Servus, Benjamin
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.
Perhaps (un)related, is the release schedule for 3.5.3 set yet? (I'm holding off putting a new version of typing.py on typeshed until that's out.)
On Mon, Nov 28, 2016 at 10:36 AM, Serhiy Storchaka storchaka@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.
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/guido% 40python.org
-- --Guido van Rossum (python.org/~guido)
On 11/28/2016 10:42 AM, Guido van Rossum wrote:
Perhaps (un)related, is the release schedule for 3.5.3 set yet? (I'm holding off putting a new version of typing.py on typeshed until that's out.)
Not set in stone, but I have a rough plan. I want the dust to settle around 3.6 first. So, have an RC1 in January, and then the final release two weeks later. I'm traveling the second week of January (#DSDad) so the RC would be either before or after that.
//arry/
On 28.11.2016 20:38, Larry Hastings wrote:
On 11/28/2016 10:42 AM, Guido van Rossum wrote:
Perhaps (un)related, is the release schedule for 3.5.3 set yet? (I'm holding off putting a new version of typing.py on typeshed until that's out.)
Not set in stone, but I have a rough plan. I want the dust to settle around 3.6 first. So, have an RC1 in January, and then the final release two weeks later. I'm traveling the second week of January (#DSDad) so the RC would be either before or after that.
https://wiki.debian.org/DebianStretch shows the final Debian release freeze for 2016-02-05, which would be a bit close for a 3.5.3 release. So anything with some buffer to Feb 05 would be appreciated.
On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka storchaka@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
Okay, by popular demand, 2.7.13 now happens in January.
I'm curious what people are planning to do to 2.7 with the extra 5 weeks. The 2.7 branch is a place to put occasional conservative bug fixes, which we aggregate and release every 6 months. It shouldn't really need special attention or become less stable depending on the release stage of Python 3.
On Mon, Nov 28, 2016, at 20:50, Raymond Hettinger wrote:
On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka storchaka@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/benjamin%40python.org
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.
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.
Top-posted from my Windows Phone
-----Original Message----- From: "Benjamin Peterson" benjamin@python.org Sent: 11/29/2016 0:04 To: "Raymond Hettinger" raymond.hettinger@gmail.com; "Serhiy Storchaka" storchaka@gmail.com Cc: "Python-Dev@Python. Org" python-dev@python.org Subject: Re: [Python-Dev] Python 2.7.13 release dates
Okay, by popular demand, 2.7.13 now happens in January.
I'm curious what people are planning to do to 2.7 with the extra 5 weeks. The 2.7 branch is a place to put occasional conservative bug fixes, which we aggregate and release every 6 months. It shouldn't really need special attention or become less stable depending on the release stage of Python 3.
On Mon, Nov 28, 2016, at 20:50, Raymond Hettinger wrote:
On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka storchaka@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/benjamin%40python.org
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/steve.dower%40python.org
same here. https://wiki.debian.org/DebianStretch shows the final Debian release freeze for 2016-02-05, which would be a bit close for a 2.7.13 release.
On 29.11.2016 15:12, Steve Dower wrote:
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.
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.
Top-posted from my Windows Phone
-----Original Message----- From: "Benjamin Peterson" benjamin@python.org Sent: 11/29/2016 0:04 To: "Raymond Hettinger" raymond.hettinger@gmail.com; "Serhiy Storchaka" storchaka@gmail.com Cc: "Python-Dev@Python. Org" python-dev@python.org Subject: Re: [Python-Dev] Python 2.7.13 release dates
Okay, by popular demand, 2.7.13 now happens in January.
I'm curious what people are planning to do to 2.7 with the extra 5 weeks. The 2.7 branch is a place to put occasional conservative bug fixes, which we aggregate and release every 6 months. It shouldn't really need special attention or become less stable depending on the release stage of Python 3.
On Mon, Nov 28, 2016, at 20:50, Raymond Hettinger wrote: >
On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka storchaka@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/benjamin%40python.org
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/steve.dower%40python.org
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/doko%40ubuntu.com
Okay, now that we're heard from the other side, and I lacking a concrete reason to delay the release, I'm putting 2.7.13 back at the original dates.
On Tue, Nov 29, 2016, at 06:34, Matthias Klose wrote:
same here. https://wiki.debian.org/DebianStretch shows the final Debian release freeze for 2016-02-05, which would be a bit close for a 2.7.13 release.
On 29.11.2016 15:12, Steve Dower wrote:
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.
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.
Top-posted from my Windows Phone
-----Original Message----- From: "Benjamin Peterson" benjamin@python.org Sent: 11/29/2016 0:04 To: "Raymond Hettinger" raymond.hettinger@gmail.com; "Serhiy Storchaka" storchaka@gmail.com Cc: "Python-Dev@Python. Org" python-dev@python.org Subject: Re: [Python-Dev] Python 2.7.13 release dates
Okay, by popular demand, 2.7.13 now happens in January.
I'm curious what people are planning to do to 2.7 with the extra 5 weeks. The 2.7 branch is a place to put occasional conservative bug fixes, which we aggregate and release every 6 months. It shouldn't really need special attention or become less stable depending on the release stage of Python 3.
On Mon, Nov 28, 2016, at 20:50, Raymond Hettinger wrote: >
On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka storchaka@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/benjamin%40python.org
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/steve.dower%40python.org
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/doko%40ubuntu.com
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/benjamin%40python.org
On Tue, 29 Nov 2016 23:07:14 -0800 Benjamin Peterson benjamin@python.org wrote:
Okay, now that we're heard from the other side, and I lacking a concrete reason to delay the release, I'm putting 2.7.13 back at the original dates.
Serhiy may be thinking about https://bugs.python.org/issue28427
Regards
Antoine.
On Wed, Nov 30, 2016, at 10:19, Antoine Pitrou wrote:
On Tue, 29 Nov 2016 23:07:14 -0800 Benjamin Peterson benjamin@python.org wrote:
Okay, now that we're heard from the other side, and I lacking a concrete reason to delay the release, I'm putting 2.7.13 back at the original dates.
Serhiy may be thinking about https://bugs.python.org/issue28427
But that isn't new, right?
On Wed, 30 Nov 2016 22:58:01 -0800 Benjamin Peterson benjamin@python.org wrote:
On Wed, Nov 30, 2016, at 10:19, Antoine Pitrou wrote:
On Tue, 29 Nov 2016 23:07:14 -0800 Benjamin Peterson benjamin@python.org wrote:
Okay, now that we're heard from the other side, and I lacking a concrete reason to delay the release, I'm putting 2.7.13 back at the original dates.
Serhiy may be thinking about https://bugs.python.org/issue28427
But that isn't new, right?
Definitely not :-)
-
Antoine Pitrou -
Benjamin Peterson -
Guido van Rossum -
Larry Hastings -
Matthias Klose -
Raymond Hettinger -
Serhiy Storchaka -
Steve Dower