Showing content from http://mail.python.org/pipermail/python-dev/attachments/20161218/65a0cd34/attachment.html below:
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
So, if you have an opinion, please vote for one of these three
options:<br>
<ul>
<li>Don't slip 3.5.3. and 3.4.6.</li>
<li>Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0.</li>
<li>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.</li>
</ul>
<br>
Your faithful servant,<br>
<br>
<br>
<i>/arry</i><br>
<br>
</body>
</html>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4