Antoine Pitrou writes: > 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.
As usual, in theory precision is infinite, but in engineering practice it's fuzzy. "Lock step" doesn't mean "as fine as you can split a second"; for 2.6/3.0 a couple of weeks separation is not going to matter. The important thing is to get right back on schedule for releasing 2.7/3.1 together (if that's the plan). Split-second precision does matter for marketing, though.<wink> _______________________________________________ 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
