Re: [python-committers] Status of the Derby, and request for another slip

On 01/26/2014 02:18 PM, Guido van Rossum wrote: On Sun, Jan 26, 2014 at 2:16 PM, Barry Warsaw > wrote: The closer Python 3.4 can stick to the March 16th release, the better. Yes. That's the whole point of time-based releases. Please stick to the plan. We've alrea

Re: [python-committers] Status of the Derby, and request for another slip

On Sun, Jan 26, 2014 at 2:16 PM, Barry Warsaw wrote: > On Jan 26, 2014, at 01:59 PM, Eli Bendersky wrote: > > >This actually sounds like a real and interesting reason to have stable > >Python 3.4 out in march. Ubuntu 14.04 is a LTS, which makes it an > important > >version for corporate distribut

Re: [python-committers] Status of the Derby, and request for another slip

On Jan 26, 2014, at 01:59 PM, Eli Bendersky wrote: >This actually sounds like a real and interesting reason to have stable >Python 3.4 out in march. Ubuntu 14.04 is a LTS, which makes it an important >version for corporate distributions. Ubuntu 14.04 feature freeze is Feb 20, with beta 1 coming o

Re: [python-committers] Status of the Derby, and request for another slip

On Sun, Jan 26, 2014 at 9:53 AM, Matthias Klose wrote: > Am 25.01.2014 14:09, schrieb Larry Hastings: > > I'd like to extend the Derby by two more weeks and add a fourth beta. > > In the past I did like the way how accurate the releases were planned and > didn't > slip at all, or only slip for a

Re: [python-committers] Status of the Derby, and request for another slip

Am 25.01.2014 14:09, schrieb Larry Hastings: > I'd like to extend the Derby by two more weeks and add a fourth beta. In the past I did like the way how accurate the releases were planned and didn't slip at all, or only slip for a few days. This may sound a bit selfish, but a few Ubuntu developers

Re: [python-committers] Status of the Derby, and request for another slip

On Jan 25, 2014, at 5:09 AM, Larry Hastings wrote: > I'd like to extend the Derby by two more weeks and add a fourth beta. There's no harm in adding a fourth beta and if it improves the release you should probably do so. We don't owe anyone a particular release date and AFAICT no one is holdin

Re: [python-committers] Status of the Derby, and request for another slip

On 26 January 2014 23:15, Tal Einat wrote: > > Having worked intensively on the Derby for over a week, I feel an urge > to see it through soon. The least we could do is to stop adding > features to clinic.py, only fixing bugs; convert everything that is > possible to convert now and mark everythin

Re: [python-committers] Status of the Derby, and request for another slip

On 26 January 2014 22:57, Serhiy Storchaka wrote: > 25.01.14 18:14, Antoine Pitrou написав(ла): > >> I don't think this is a killer feature that would deserve an extension >> of the release cycle. The feature freeze period is meant for bug fixing, >> not to shoehorn the latest bangs and whistles.

Re: [python-committers] Status of the Derby, and request for another slip

On Sat, Jan 25, 2014 at 3:09 PM, Larry Hastings wrote: > To be honest I have absolutely no idea what % of files have been converted > so far. Figuring it out would use time that would be better spent catching > up on my to-do list. Of the 22 Derby issues: * 2 have been closed: 20133 (audioop) an

Re: [python-committers] Status of the Derby, and request for another slip

25.01.14 18:14, Antoine Pitrou написав(ла): I don't think this is a killer feature that would deserve an extension of the release cycle. The feature freeze period is meant for bug fixing, not to shoehorn the latest bangs and whistles. Normally the whole Derby thing should already have waited for

Re: [python-committers] Status of the Derby, and request for another slip

On 26 January 2014 02:14, Antoine Pitrou wrote: > > On dim., 2014-01-26 at 01:40 +1000, Nick Coghlan wrote: >> I think an extra beta is still a good idea, though - I'd like to get >> at least the builtins that are already supported converted, since that >> clearly demonstrates the benefits the too

Re: [python-committers] Status of the Derby, and request for another slip

On 25/01/14 19:33, Ethan Furman wrote: > On 01/25/2014 07:40 AM, Nick Coghlan wrote: >> >> Basically, I suggest implementing the current bug fixes & minor >> features AC patch you're working on, and then calling it done >> for 3.4, with only outright bugs in existing conversions to be >> fixed be

Re: [python-committers] Status of the Derby, and request for another slip

On 01/25/2014 07:40 AM, Nick Coghlan wrote: Basically, I suggest implementing the current bug fixes & minor features AC patch you're working on, and then calling it done for 3.4, with only outright bugs in existing conversions to be fixed before 3.5. [...] I think an extra beta is still a good

Re: [python-committers] Status of the Derby, and request for another slip

On sam., 2014-01-25 at 17:14 +0100, Antoine Pitrou wrote: > On dim., 2014-01-26 at 01:40 +1000, Nick Coghlan wrote: > > I think an extra beta is still a good idea, though - I'd like to get > > at least the builtins that are already supported converted, since that > > clearly demonstrates the benefi

Re: [python-committers] Status of the Derby, and request for another slip

On dim., 2014-01-26 at 01:40 +1000, Nick Coghlan wrote: > I think an extra beta is still a good idea, though - I'd like to get > at least the builtins that are already supported converted, since that > clearly demonstrates the benefits the tool is designed to bring in > reducing the discrepancies

Re: [python-committers] Status of the Derby, and request for another slip

Larry Hastings wrote: > Please vote for either "continue the Derby" (which also means slipping the > schedule and adding a fourth beta) or "stop the Derby". I think releasing 3.4 on time is more important than adding internal changes that most people won't see at all. So I vote for releasing acc

Re: [python-committers] Status of the Derby, and request for another slip

On 25 January 2014 23:49, Larry Hastings wrote: > On 01/25/2014 05:35 AM, Antoine Pitrou wrote: > > Stop the Derby. We needn't convert everything for 3.4 (I didn't even > know that was your goal). > > > Converting everything was my goal at one point. At this point it is nowhere > near viable, not

Re: [python-committers] Status of the Derby, and request for another slip

On 01/25/2014 05:35 AM, Antoine Pitrou wrote: Stop the Derby. We needn't convert everything for 3.4 (I didn't even know that was your goal). Converting everything was my goal at one point. At this point it is nowhere near viable, not the least because there simply isn't enough time. As disc

Re: [python-committers] Status of the Derby, and request for another slip

On sam., 2014-01-25 at 05:09 -0800, Larry Hastings wrote: > > Please vote for either "continue the Derby" (which also means slipping > the schedule and adding a fourth beta) or "stop the Derby". Stop the Derby. We needn't convert everything for 3.4 (I didn't even know that was your goal). Regard