On Mon, Sep 8, 2008 at 5:22 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote: > Christian Heimes <lists <at> cheimes.de> writes: >> >> Ok, from the marketing perspective it's a nice catch to release 2.6 and >> 3.0 on the same day. "Python 2.6.0 and 3.0.0 released" makes a great >> headline. > > It's not only the marketing. Having both releases in lock step means the > development process is synchronized between trunk and py3k, that there is no > loss of developer focus, and that merges/backports happen quite naturally.
I think that we've reached the point where very few things are merged from 2.6 to 3.0 -- I see a lot more "block" commits than "merge" commits lately. Also, the added activity in 3.0 doesn't involve merges at all, because it's all 3.0-specific. Sure, we lose the ability to add last-minute -3 warnings. But I think that's a pretty minor issue (and those warnings have a tendency to subtly break things occasionally, so we shouldn't do them last-minute anyway). > But I don't think it's an overwhelming argument either. I would value it at > around 50 euro cents, not even the price of a good croissant ;-) -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
