Re: [python-committers] [Python-Dev] Should I delay 3.5.3 and 3.4.6 by two weeks?

2016-12-18 Thread Ned Deily 
On Dec 19, 2016, at 00:26, Larry Hastings  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
  [email protected] -- []

___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Should I delay 3.5.3 and 3.4.6 by two weeks?

2016-12-18 Thread Larry Hastings 



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/

___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/