Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and 3.4.6 to ship about a month after 3.6.0 did, to "let the dust settle" around the release. I expect a flood of adoption of 3.6, and people switching will find bugs, and maybe those bugs are in 3.5 or 3.4. So it just seemed sensible.
3.6 just slipped by two weeks. So now there's less than two weeks between 3.6.0 final shipping and tagging the release canddiates for 3.5.3 and 3.4.6. This isn't as much time as I'd like.
If I had total freedom to do as I liked, I'd slip my releases by two weeks to match 3.6. But there might be people planning around 3.5.3 and 3.4.6--like Guido was waiting for 3.5.3 for something iirc.
So, if you have an opinion, please vote for one of these three options:
- Don't slip 3.5.3. and 3.4.6.
- Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0.
- Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the ability to slip again without us having to change the release.
Your faithful servant,
//arry/
On Dec 19, 2016, at 00:26, Larry Hastings larry@hastings.org wrote:
Python 3.6.0 final just slipped by two weeks.
While it should not affect decisions about 3.5.3 and 3.4.6, so there's no confusion: the 3.6.0 release date slipped one week, from 2016-12-16 to 2016-12-23. Of course, until the release happens, it's possible that it could slip again but it hasn't yet and we are going to do our best to keep it from doing so.
-- Ned Deily nad@python.org -- []
On Dec 18, 2016, at 9:26 PM, Larry Hastings larry@hastings.org wrote:
So, if you have an opinion, please vote for one of these three options: • Don't slip 3.5.3. and 3.4.6. • Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0. • Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the ability to slip again without us having to change the release.
I vote for not slipping. 2.7.13 is out. 3.6.0 is almost out. And it would be nice to have the others done as well. That way, we know the whole source tree is open and can start moving forward without reservations.
Also, I would like the 3.6.0 announcement to not get drowned-out or attenuated by other announcements around older releases (i.e. it would be nice if 3.6.0 was the actual latest release of any version for a while).
Raymond
Le 19/12/2016 à 06:26, Larry Hastings a écrit :
So, if you have an opinion, please vote for one of these three options:
- Don't slip 3.5.3. and 3.4.6.
- Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0.
- Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the ability to slip again without us having to change the release.
I would myself vote for a delay. How long exactly doesn't really matter.
Motivation : I would like a fix for https://bugs.python.org/issue28427 to get in 3.5.3. The fix is ready but a quick look by the current dict specialists may be welcome (though I can do without as well :-)). Reviewer workforce may be scarce especially around end-of-Gregorian-year festivities.
Regards
Antoine.
On 19.12.2016 06:26, Larry Hastings wrote:
Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and 3.4.6 to ship about a month after 3.6.0 did, to "let the dust settle" around the release. I expect a flood of adoption of 3.6, and people switching will find bugs, and maybe those bugs are in 3.5 or 3.4. So it just seemed sensible.
3.6 just slipped by two weeks. So now there's less than two weeks between 3.6.0 final shipping and tagging the release canddiates for 3.5.3 and 3.4.6. This isn't as much time as I'd like.
If I had total freedom to do as I liked, I'd slip my releases by two weeks to match 3.6. But there might be people planning around 3.5.3 and 3.4.6--like Guido was waiting for 3.5.3 for something iirc.
So, if you have an opinion, please vote for one of these three options:
- Don't slip 3.5.3. and 3.4.6.
- Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0.
- Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the ability to slip again without us having to change the release.
I would appreciate a 3.5.3 release which doesn't slip, or which only slips by a week, to be available before the Debian freeze. Neither Debian nor Ubuntu ship the 3.4 branch anymore, so for 3.4 I'm fine with any solution.
Matthias
100% of votes cast were for "don't slip", so we won't slip.
Retreat! Full steam behind!
//arry/
On 12/20/2016 02:25 AM, Matthias Klose wrote:
On 19.12.2016 06:26, Larry Hastings wrote:
Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and 3.4.6 to ship about a month after 3.6.0 did, to "let the dust settle" around the release. I expect a flood of adoption of 3.6, and people switching will find bugs, and maybe those bugs are in 3.5 or 3.4. So it just seemed sensible. 3.6 just slipped by two weeks. So now there's less than two weeks between 3.6.0 final shipping and tagging the release canddiates for 3.5.3 and 3.4.6. This isn't as much time as I'd like. If I had total freedom to do as I liked, I'd slip my releases by two weeks to match 3.6. But there might be people planning around 3.5.3 and 3.4.6--like Guido was waiting for 3.5.3 for something iirc. So, if you have an opinion, please vote for one of these three options: * Don't slip 3.5.3. and 3.4.6. * Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0. * Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the ability to slip again without us having to change the release.
I would appreciate a 3.5.3 release which doesn't slip, or which only slips by a week, to be available before the Debian freeze. Neither Debian nor Ubuntu ship the 3.4 branch anymore, so for 3.4 I'm fine with any solution. Matthias
-
Antoine Pitrou -
Larry Hastings -
Matthias Klose -
Ned Deily -
Raymond Hettinger